Exercise 7 ( Chapter 13 )

Exercise 7 (Chapter 13)

Q1:

Break out and estimate testing tasks for the following story from the Xtrack application. This is the same story for which you defined acceptance tests in Exercise 4, so use those or our answer to that exercise as a starting point:

Story: User can create, update, display, and delete a task. A task has a name, a description, assignee, estimate, actual time spent, state, and created/updated timestamps.

A1:

Here are the tests we defined for Exercise 4:

Tests for Exercise 4
Action	Data	Expected Result
1. Add a new task	An existing story, values for the task fields	Success: the task is added
2.	An existing story, values only for task name, description, and state	Success: none of these is a required field
3.	An existing story, no values for task name, description, and state	Failure: these are required fields
4. Select an existing task and update	An existing task, new values for estimate, assignee	Success: task fields are updated
5.	An existing task, empty values for description, status	Failure: these are required fields
6. Select a task and click to delete	An existing task	Success: task is deleted

Functional and Acceptance Testing Tasks

1. We need to work with the customer to define detailed acceptance tests that will include all the details not provided in the high-level tests. (This includes defining error messages, verifying look and feel of the input form and display list, defining typical and potentially tricky user scenarios. Because this is an internal application that will be used mainly by trained users, we don't need to worry about this as much as we would for an external product.) We estimate 1 hour.

2. It should be pretty easy to define and load this test data. We just need data for some existing stories and some tasks. Neither has very many fields. We estimate 0.5 hour.

3. We think we're probably going to need to code three automation modules for this: addTask, updateTask, and deleteTask. They're all pretty similar, so we figure an hour to spike the automation and an hour to code and test each. We estimate 4 hours.

4. Setting up and executing tests will be fast, but we'll probably run them at least three times. We estimate 0.5 hour.

5. Same with evaluation and reporting results. We estimate 0.5 hour.

Here are our tasks and estimates:

Tasks and estimates for Exercise 7
Task	Estimate (hours)
Define task story details	1.0
Define and create test data	0.5
Code and test addTask module	2.0
Code and test updateTask module	1.0
Code and test deleteTask module	1.0
Test execution	0.5
Reporting	0.5
Total	6.5