Scribd
Upload
33 views

ECSE429 Assignment 2

Assignment #2 requires students to complete exploratory testing of a REST API todo list manager application in groups. They must conduct testing sessions exploring capabilities related to todos, projects, categories or interoperability. For each session, they must document findings, concerns, bugs and ideas for future testing.

Uploaded by

1mysterious.iam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
33 views

ECSE429 Assignment 2

Assignment #2 requires students to complete exploratory testing of a REST API todo list manager application in groups. They must conduct testing sessions exploring capabilities related to todos, projects, categories or interoperability. For each session, they must document findings, concerns, bugs and ideas for future testing.

Uploaded by

1mysterious.iam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Assignment #2 ECSE429 / Fall 2021

Assignment #2 – Exploratory Testing


Assignment #2 is completed in groups of two students (i.e. the same group as for Assignment #1). It
is due on Sunday, October 10th at 11:59pm and it is worth 5% of the final mark.

For this assignment, your team is required to submit a report to address the challenges below. The
report must be provided as a Wiki page in the GitHub repository of your team (which is the same
repository as the one used for Assignment #1). The report must contain all the items that are asked
to be documented for the individual problems.

Submission of deliverable: Your team is required to work on the deliverables in the repository
assigned to your team in the GitHub organization of this course, but a commit link of your wiki page
(i.e. the URL of your final commit before the deadline) is required to be submitted in myCourses. To
get a commit link, you need to select the Wiki tab your repository and click on “Revisions”, where
URL of the commit link can be copied after selecting (right-clicking) the hash code of the commit:

Application Under Test

The application under test is a “rest api todo list manager” which may be run on localhost. A copy of
the application is available in myCourses or it could be downloaded from here.

The application is made available by Alan Richardson and it can be found online at:
https://github.com/eviltester/thingifier

Setup:

1. Navigate to the source directory of the jar file in the terminal.


2. Launch the rest api todo list manager with the command:
java -jar runTodoManagerRestAPI-1.5.5.jar

Configuration Files:

Basic documentation about the rest api todo list manager is found at: http://localhost:4567/docs

A Swagger description of the rest api todo list manager is referenced in the documentation and can
be found at the link: http://localhost:4567/docs/swagger

Individuals interested in learning about or using Swagger may benefit from a free individual account
at: https://swagger.io/tools/
Assignment #2 ECSE429 / Fall 2021

Problem #1.1 – Exploratory Testing (100 marks)


Consider the following charter for exploratory testing:

Identify capabilities and areas of potential instability of the “rest api todo list manager”.
Identify documented and undocumented “rest api todo list manager” capabilities.
Exercise each capability identified with data typical to the intended use of the application.

• Team members are required to use (charter-driven) Session Based Exploratory Testing to
study the behavior of the “rest api todo list manager”.
• Team members will do exploratory testing sessions in pairs. Both team members must
participate in exploratory testing sessions.
• Each exploratory testing session should be timeboxed at 45 minutes.
• Each team must perform exploratory testing on capabilities related to two things
(one/member) from various options available todos, projects, categories and interoperability.

Deliverable (for each session)

• Session notes (please follow this structure as a template: https://github.com/McGill-


ECSE429-Fall2021/Assignment-Deliverables/wiki/A2:-Exploratory-Testing)
o Explicitly reference any scripts, programs, screen shots, video clips, spreadsheets or
any other files used in or created during the session.
o Include name and email address of session participants.
• Include any files created in the session.
• Summary of session findings
o This is a bullet list created when the session findings are reviewed.
o This list answers the question what we learned.
• A document with the list of concerns and new testing ideas identified in the session.
• Bug summary document.

In addition, please include a short report describing the overall findings of the complete exploratory
testing (i.e. both the sessions).

Bug Summary Considerations

The project team should define a form used to collect bug information which includes at least the
following elements.

o Executive summary of bug in 80 characters or less


o Description of bug
o Potential impact of bug on operation of system
o Steps to reproduce the bug
Assignment #2 ECSE429 / Fall 2021

Structure of Deliverable:

You need to structure the Wiki pages of your deliverable as follows:

A2-Exploratory_Testing {team_number}
├── Findings report/
├── Session1_{capability_name}/
├ ├── Session_note
├ ├── Session_summary
├ ├── Bug_Summary
├ ├── Concerns_testingideas
├ ├── Any other file created during session (optional)
├──Session2_{capability_name}/
…
├── Any other file for reference (optional)

Individual contributions. Each team member must make contributions to the assignment. A team
member who does not contribute to the assignment receives a mark of 0 for the assignment. A team
member may optionally email a confidential statement of work to the instructor before the due date
of the assignment. A statement of work first lists in point form the parts of the assignment to which
the team member contributed. In addition, the statement of work also describes whether the work
load was distributed fairly evenly among the team members. A statement of work may be used to
adjust the mark of a team member who is not contributing sufficiently to the assignment. It is not
necessary to send a statement of work, if a team distributed the work for the assignment fairly evenly
and each team member contributed sufficiently.

You might also like