Testing Scenarios

8/12/2019 Testing Scenarios

http://slidepdf.com/reader/full/testing-scenarios 1/101









Release #XXProject: #123456 Enter project name

Past Test Cycles Trend

Test Cycle Test Results

Total Failed

1 Beta 1.00 Release 109 15 40.4 h

2 RTM 1.00 Release 356 24 111.3 h

3 RTM 1.01 Release 379 16 90.8 h

4 RTM 1 02 R l 412 14 92 3 h

Test CycleName#

Test Case

Counts

Total

TestTime

0

100

200

300

400

500

600

1 2 3 4 5 6 7 8 9 10

Test Cycle

0.0 h

20.0 h

40.0 h

60.0 h

80.0 h

100.0 h

120.0 h

1 2 3 4 5 6 7 8 9 10

Test Cycle

Total Test Case Counts Total Test Time

0

510

15

20

25

30

1 2 3 4 5 6 7 8 9 10

Test Cycle

Failed Test Case Counts

TCM Lite





Instructions

text Type your project data into the white cells

text Type section header names into the blue cells

text Do no t type over gray cells, especially those with formulas

Title Do no t type over dark gray column title cells

Title Do no t type over black title cells

Title Do no t alter graphs, they will automatically re-calculate and re-size as needed

1 - Quick Start Guide

Introduction

Test Case Manager Lite (TCMLite hereafter) is a simple tool designed for software test engineers to organize test cases

for storage and execution logging. Once test cases are built, testers use TCM to track and report success, failure, or

blocking of test cases.

TCMLite has no size or install limitations. Use it an unlimited number of times as a central, multi-user app (yes, XLsupports concurrent usage and merge-conflict-resoluton...see section 1.4 in the QuickStart section). TCMLite is

intended for use by small to midsize software development teams. TCM was designed to be easy to learn and use.

1.1 - General Data Entry Rules:In general, you only type into white cells, or blue section title cells, and nothing else.

Use the following key:

To change Test Area names, you must rename the worksheets (highlighted in yellow below) by double-clicking them. All

references to these test areas will automatically update throughout the spreadsheet immediately after making your

changes.



1.

2.

1. Select Tools >> Share Workbook from XL's menu (see [A] below):

Often, there is more than one tester working a given project. It is thus crucial to share the project test case spreadsheetout on a file share so that multiple testers can concurrently follow test steps and log results. Microsoft Excel has a

"shared workbook" mode that allows for this, including managing merging (whose entries win) should two users alter the

same cell.

Follow these steps to put the spreadsheet in mutli-user mode:

Once you have the base set of test cases built for a project, you will often want to clean out the Status field to capture

results for a new test cycle. For example, you may have a regression suite of 450 test cases that you run through every

major release. After creating a new copy of the most recent spreadsheet, you may need to clean out its results. Do so

as follows:

1.4 - Multi-User Shared Mode:

1.3 - Reset Test Case Execution Status for a New Test Cycle:

Search and Replace (ctrl-H) the letter 'P' with the letter 'U' ( [A] below). This will reset status to Untested (from

Pass). Be sure to check "Match case" and "Find entire cells only" ( [B] below) to ensure that only the contents of

column "Status" get changed throughout the spreadsheet.

Repeat Search and Replace for the letters 'F', 'B', and 'S' also, changing them back to 'U' for the next test cycle.

1AB

A



1.5 - Context-Sensitive Help:Hover the mouse-pointer over any Excel red comment indicator (see [A] below) for a popup help tip (see [B] below).

A

B



2 - Current Test Cycle Snapshot

2.1 - Worksheet Definition:This is the first tab in the spreadsheet, titled "Snapshot". The data in this report summarizes all test cases and test

results at a single point in time (now). Print or PDF this single page report out to check status at daily stand-up meetingsor to update management on the current test-cycle status.

A

B

C E

G

D

F

H





3 - Past Test Cycles Trend

3.1 - Worksheet Definition:

The data from this table is used to populate the test result graphs in 2.G above. The test case counts column, and the

percent of total test case counts column are the most useful bits of information in this table. When asked by key

stakeholders how testing is going, you can quickly respond with the untested and blocked counts remaining, or the

percent of test case yet to execute. As you dial in and firm up your test cases, the test time become exclusively

execution time (no research, no writing) and you can also use the untested + blocked test times to estimate how muchtime remains to completion.

This is the second tab in the spreadsheet, titled "Trend". The data in this report summarizes all test cases and test

results accross time, taken at the end of every test cycle. Print or PDF this single page report out at the end of yoru test

cycle and reference it during the project post mortem. Did you increase test coverage (test case counts)? Did you

decrease failed test case counts? Did you noticeably improve efficiency (decrease total test time relative to test case

count)?

For the first couple of test cycles, there is no data and no trends. By the third cycle, this report becomes more useful and

you can start to see some trends.

2.H - Test Result Table:

A B

C E

D



3.D - Failed Test Case Count Graph:

Do not type over this text; it is automatically pulled from the worksheet Snapshot's Test Cycle section's Test Cycle Name

field (see [D] above), and the project number and project name in the second line are pulled from the Project Information

section (see [E] above).

3.C - Total Test Case Count Graph:

Replace the sample logo (Acme sample company logo) with your company's logo. Just highlight and delete the sample

logo in the template, then paste in your company's logo.

This graph depicts the total test case count over time. It represents test case coverage.

This bar chart shows the total test time from past test cycles. At first, test times will be high because they include time to

research the test case, time to write-up and refine the test case, and time to execute the test case and log results. All

subsequent test cycles will only require execution and logging times, thus total test time should diminish. Also, familiarity

should enable you to manually execute the test cases faster and faster. At some point you should further improve

efficiency by automating groups of test cases.

3.A - Company Logo:

3.B - Report Title: Test Cycle Name + Project Number & Project Name:

3.F - Test Cycle Test Results:Here is where you do data entry to populate all the graphs on the page. Take the data from the "Snapshot" worksheet at

the end of each test cycle, and type it in here. The test case counts, and total test time are taken from the "Snapshot"

worksheet's Test Results Table.

To clear out the sample data for a new project, just highlight and delete all the values in the white cells (but leave the

gray cell formulas as-is).

To delete unused rows, highlight the entire row(s) by selecting the row number, right-click, and select delete. The

graphs will all automatically adjust scale.

To insert new rows so you can add more test cycles highlight one existing row and copy it Then highlight one or more

This graph depicts the failed test case count over time. As the application matures, failed test case counts should drop.

3.E - Total Test Time:



4 - Test Case / Test Area Worksheets

4.1 - Worksheet Definition:There are twenty of these worksheet tabs in the spreadsheet. These worksheets are where you do most of your work

and where most of the value of test case management originates. Here is where you lgocially group your test cases by

test area across worksheet tabs, and by user story or use case (blue highlight rows) within each worksheet. Here is

where you track test case execution results (pass, fail, block, etc.).

A

B C

DE F G

H

I J

K L

M

G



●

●

●

●

●

●

●

●

●

●

●

●

●

●

Enter the expected results for the test steps entered.

Be sure to separate each expected result on a separate line so that the status applies to individual test results.

Suggest labeling each separate result on separate lines with separate letters (A., B., C., etc.)

4.G - Test Result Column:

White background = Done (Pass, n/a, and Skip)

Key in P, F, S, B, U, or n/a

Type-over sample test steps

4.D - Test Case Number Column:These values are calculated; do not type over.

Occasionally, using copy-paste to insert new rows will yield incorrect TC#'s because the cell references got

shifted. Fix this either by correcting the references, or copy-paste a different cell with same formula from same

column.

4.E - Test Execution Steps Column:

Hover mousepointer and use the drop down

Note: Do not change the backcolor, it is automatically formatted based on the text in the cell.

4.H - Date Tested Column:This column is the date of test execution. You enter this value at the same time you assign a test result of pass or fail.

There are two quick shortcuts to quickly entering the date value:

Use "alt-enter" to enter text on next line of same cell (that's how the sample data has step numbers listed)

Ensure that all test steps lead to a single expected result. Insert new lines as necessary to add additional

expected results, then merge the multiple row-cells of test steps into a single cell spanning all expected results.

4.F - Expected Result Column:

This column is where you track test results. Every test cycle you reset these values to U (untested) following the

instructions laid out in section 1.3.

Here are the standard cell color coding conventions:

Two ways to enter a status value:

Red background = Fail

Yellow background = Blocked

Light yellow background = Untested



●

●

1.

2.

3.

Highlight an empty source row:

Press ctrl-C to copy the highlighted row

Highlight the target row(s) which will be inserted down when you insert-paste the source empty test case row.

Note that you can paste multiple new rows from the single highlighted source row as shown in the screenshot

below (by highlighting several target rows):

4.2 - Copy-Inserting New Test Case Rows:The test case worksheets come defaulted with 50 test case rows per worksheet. You may quickly find the need to copy

and insert-paste new untested test case rows. If you simply highlight a row and paste, you will overwrite the row's

contents, not insert a new copy of the source row.

To insert one or more copied rows, follow these steps:

Highlight a cell in this Column, then press ctrl-up or ctrl-down to quickly jump up and down through the list, landing

on those rows that you bookmarked with an X.

4.L - Bookmark Column:Enter X's on rows that you want to quickly jump to such as Status = F or B

A



4.

5.

5 - Managing Test Cases

Right-click and select "Insert Copied Cells" from the context menu. Since I highlighted 4 rows, this operation will

paste four copies of the one source row:

Resulting in TC's #51-54 (black rows 65-68) being added. This is how you paste-insert new rows while still

preserving drop down values in the Test Results column, and more importantly preserving the automatic counts in

graphs and charts.

5.1 - Organizing Test Cases:One of the most important parts of developing a test case repository within TCMLite is to plan the layout (breakdown) of

the various test areas. The primary goal of the layout is to provide a structure that will be immediately obvious to a tester

familiar with the product. We suggest that you use the Test Specification you built on paper; or follow the major features



●

● DO NOT give setup or repro steps unless they are necessary. Anotherwords, if the test case should start off at a

well known form, then just list that one step in the setup steps (start at form X). You do not need to list all the

steps to get to that form too, unless it is an obscure dialog and it would help new testers.

DO NOT use test files or other attachments unless clearly helpful. If so, try to have the creation of the test file be

part of the test case. Also, put these attachments on a UNC shared folder on your network, and only put the

reference path here in the comments column of the given test case. Ensure other testers on your team have

access to the share.









Test Case ResultsU 7 64% 0.0 h

P 1 9% 0.3 h

F 1 9% 0.8 h

S 1 9% 0.0 h

B 1 9% 0.4 h

TC# Test Execution Steps Expected Result

Test

Result

Date

Tested Tester

TC

Time

Comment /

(or Requirement xref)

1 P 15 m

2 F 50 m

3 S 1 m

4 B 25 m

5 U

6 U

7 U

8 U9 U

10 U

11 U

12 n/a

13 n/a

14 n/a

15 n/a

16 n/a

17 n/a

18 n/a19 n/a

20 n/a

21 n/a

22 n/a

23 n/a

24 n/a

25 n/a

26 n/a

27 n/a

28 n/a

29 n/a30 n/a

31 n/a

32 n/a

1 - A

User Story -

0 2 4 6 8 1 0

1 2

P

F

B

U

S



33 n/a

34 n/a

35 n/a

36 n/a

37 n/a

38 n/a

39 n/a

40 n/a

41 n/a42 n/a

43 n/a

44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a

Copy test case rows and ins ert-paste here to shif t dow n the gray l ines and preserve the autom atic calculat ions.







Test Case ResultsU 0 - 0.0 h

P 0 - 0.0 h

F 0 - 0.0 h

S 0 - 0.0 h

B 0 - 0.0 h


Test

Result

Date

Tested Tester

TC

Time

Comment /


1 n/a

2 n/a

3 n/a

4 n/a

5 n/a

6 n/a

7 n/a

8 n/a9 n/a

10 n/a

11 n/a

12 n/a

13 n/a

14 n/a

15 n/a

16 n/a

17 n/a

18 n/a19 n/a

20 n/a

21 n/a

22 n/a

23 n/a

24 n/a

25 n/a

26 n/a

27 n/a

28 n/a

29 n/a

30 n/a

31 n/a

32 n/a

2 - X

User Story -

0

1 2 9

2 5 8

3 8 7

5 1 6

P

F

B

U

S



33 n/a

34 n/a

35 n/a

36 n/a

37 n/a

38 n/a

39 n/a

40 n/a

41 n/a42 n/a

43 n/a

44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a






3 X




P 0 - 0.0 h

F 0 - 0.0 h

S 0 - 0.0 h

B 0 - 0.0 h


Test

Result

Date

Tested Tester

TC

Time

Comment /


1 n/a

2 n/a

3 n/a

4 n/a

5 n/a

6 n/a

7 n/a

8 n/a9 n/a

10 n/a

11 n/a

12 n/a

13 n/a

14 n/a

15 n/a

16 n/a

17 n/a

18 n/a19 n/a

20 n/a

21 n/a

22 n/a

23 n/a

24 n/a

25 n/a

26 n/a

27 n/a

28 n/a

29 n/a30 n/a

31 n/a

32 n/a

3 - X

User Story -

0

1 2 9

2 5 8

3 8 7

5 1 6

P

F

B

U

S

33 n/a



33 n/a

34 n/a

35 n/a

36 n/a

37 n/a

38 n/a

39 n/a

40 n/a

41 n/a42 n/a

43 n/a

44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a






4 - X




P 0 - 0.0 h

F 0 - 0.0 h

S 0 - 0.0 h

B 0 - 0.0 h


Test

Result

Date

Tested Tester

TC

Time

Comment /


1 n/a

2 n/a

3 n/a

4 n/a

5 n/a

6 n/a

7 n/a

8 n/a9 n/a

10 n/a

11 n/a

12 n/a

13 n/a

14 n/a

15 n/a

16 n/a

17 n/a

18 n/a19 n/a

20 n/a

21 n/a

22 n/a

23 n/a

24 n/a

25 n/a

26 n/a

27 n/a

28 n/a

29 n/a30 n/a

31 n/a

32 n/a

4 X

User Story -

0

1 2 9

2 5 8

3 8 7

5 1 6

P

F

B

U

S

33 n/a



34 n/a

35 n/a

36 n/a

37 n/a

38 n/a

39 n/a

40 n/a

41 n/a42 n/a

43 n/a

44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a






5 - X




P 0 - 0.0 h

F 0 - 0.0 h

S 0 - 0.0 h

B 0 - 0.0 h

TC# Test Execution Steps Expected ResultTest

ResultDate

Tested Tester TC

TimeComment /


1 n/a

2 n/a

3 n/a

4 n/a

5 n/a

6 n/a

7 n/a

8 n/a9 n/a

10 n/a

11 n/a

12 n/a

13 n/a

14 n/a

15 n/a

16 n/a

17 n/a

18 n/a

19 n/a

20 n/a

21 n/a

22 n/a

23 n/a

24 n/a

25 n/a

26 n/a

27 n/a

28 n/a

29 n/a30 n/a

31 n/a

32 n/a

User Story -

0

1 2 9

2 5 8

3 8 7

5 1 6

P

F

B

U

S

33 n/a

34 n/a



34 n/a

35 n/a

36 n/a

37 n/a

38 n/a

39 n/a

40 n/a

41 n/a42 n/a

43 n/a

44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a






6 - X




P 0 - 0.0 h

F 0 - 0.0 h

S 0 - 0.0 h

B 0 - 0.0 h


ResultDate

Tested Tester TC

TimeComment /


1 n/a

2 n/a

3 n/a

4 n/a

5 n/a

6 n/a

7 n/a

8 n/a9 n/a

10 n/a

11 n/a

12 n/a

13 n/a

14 n/a

15 n/a

16 n/a

17 n/a

18 n/a

19 n/a

20 n/a

21 n/a

22 n/a

23 n/a

24 n/a

25 n/a

26 n/a

27 n/a

28 n/a

29 n/a30 n/a

31 n/a

32 n/a

User Story -

0

1 2 9

2 5 8

3 8 7

5 1 6

P

F

B

U

S

33 n/a

34 n/a



35 n/a

36 n/a

37 n/a

38 n/a

39 n/a

40 n/a

41 n/a42 n/a

43 n/a

44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a








33 n/a

34 n/a

35 n/a



35 n/a

36 n/a

37 n/a

38 n/a

39 n/a

40 n/a

41 n/a42 n/a

43 n/a

44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a






Test Case Results

8 - X

P



U 0 - 0.0 h

P 0 - 0.0 h

F 0 - 0.0 h

S 0 - 0.0 h

B 0 - 0.0 h


ResultDate

Tested Tester TC

TimeComment /


1 n/a

2 n/a

3 n/a

4 n/a

5 n/a

6 n/a

7 n/a

8 n/a9 n/a

10 n/a

11 n/a

12 n/a

13 n/a

14 n/a

15 n/a

16 n/a

17 n/a

18 n/a

19 n/a20 n/a

21 n/a

22 n/a

23 n/a

24 n/a

25 n/a

26 n/a

27 n/a

28 n/a

29 n/a30 n/a

31 n/a

32 n/a

User Story -

0

1 2 9

2 5 8

3 8 7

5 1 6

F

B

U

S







Test Case ResultsU 0 - 0 0 h

9 - X

P

F



U 0 - 0.0 h

P 0 - 0.0 h

F 0 - 0.0 h

S 0 - 0.0 h

B 0 - 0.0 h


ResultDate

Tested Tester TC

TimeComment /


1 n/a

2 n/a

3 n/a

4 n/a

5 n/a

6 n/a

7 n/a

8 n/a

9 n/a

10 n/a

11 n/a

12 n/a

13 n/a

14 n/a

15 n/a

16 n/a

17 n/a

18 n/a

19 n/a20 n/a

21 n/a

22 n/a

23 n/a

24 n/a

25 n/a

26 n/a

27 n/a

28 n/a

29 n/a30 n/a

31 n/a

32 n/a

User Story -

0

1 2 9

2 5 8

3 8 7

5 1 6

F

B

U

S

33 n/a

34 n/a

35 n/a

36 n/a



36 n/a

37 n/a

38 n/a

39 n/a

40 n/a

41 n/a

42 n/a

43 n/a

44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a







10 - X

P

F



P 0 - 0.0 h

F 0 - 0.0 h

S 0 - 0.0 h

B 0 - 0.0 h


ResultDate

Tested Tester TC

TimeComment /


1 n/a

2 n/a

3 n/a

4 n/a

5 n/a

6 n/a

7 n/a

8 n/a

9 n/a

10 n/a

11 n/a

12 n/a

13 n/a

14 n/a

15 n/a

16 n/a

17 n/a

18 n/a

19 n/a20 n/a

21 n/a

22 n/a

23 n/a

24 n/a

25 n/a

26 n/a

27 n/a

28 n/a

29 n/a

30 n/a

31 n/a

32 n/a

User Story -

0

1 2 9

2 5 8

3 8 7

5 1 6

B

U

S








P 0 - 0 0 h

11 - X

P

F

B



P 0 0.0 h

F 0 - 0.0 h

S 0 - 0.0 h

B 0 - 0.0 h

TC# Test Execution Steps Expected Result TestResult DateTested Tester TCTime Comment /(or Requirement xref)

1 n/a

2 n/a

3 n/a

4 n/a

5 n/a

6 n/a

7 n/a

8 n/a

9 n/a10 n/a

11 n/a

12 n/a

13 n/a

14 n/a

15 n/a

16 n/a

17 n/a

18 n/a

19 n/a20 n/a

21 n/a

22 n/a

23 n/a

24 n/a

25 n/a

26 n/a

27 n/a

28 n/a

29 n/a

30 n/a

31 n/a

32 n/a

User Story -

0

1 2 9

2 5 8

3 8 7

5 1 6

B

U

S

33 n/a

34 n/a

35 n/a

36 n/a

37 n/a



37 n/a

38 n/a

39 n/a

40 n/a

41 n/a

42 n/a43 n/a

44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a







P 0 - 0.0 h

12 - X

P

F

B



F 0 - 0.0 h

S 0 - 0.0 h

B 0 - 0.0 h


Test

Result

Date

Tested Tester

TC

Time

Comment /


1 n/a

2 n/a

3 n/a

4 n/a

5 n/a

6 n/a

7 n/a

8 n/a

9 n/a10 n/a

11 n/a

12 n/a

13 n/a

14 n/a

15 n/a

16 n/a

17 n/a

18 n/a

19 n/a20 n/a

21 n/a

22 n/a

23 n/a

24 n/a

25 n/a

26 n/a

27 n/a

28 n/a

29 n/a

30 n/a31 n/a

32 n/a

User Story -

0

1 2 9

2 5 8

3 8 7

5 1 6

U

S

33 n/a

34 n/a

35 n/a

36 n/a

37 n/a



38 n/a

39 n/a

40 n/a

41 n/a

42 n/a43 n/a

44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a







P 0 - 0.0 h

F 0 - 0.0 h

13 - X

P

F

B

U



F 0 0.0 h

S 0 - 0.0 h

B 0 - 0.0 h


Test

Result

Date

Tested Tester

TC

Time

Comment /


1 n/a

2 n/a

3 n/a

4 n/a

5 n/a

6 n/a

7 n/a

8 n/a

9 n/a10 n/a

11 n/a

12 n/a

13 n/a

14 n/a

15 n/a

16 n/a

17 n/a

18 n/a

19 n/a20 n/a

21 n/a

22 n/a

23 n/a

24 n/a

25 n/a

26 n/a

27 n/a

28 n/a

29 n/a

30 n/a31 n/a

32 n/a

User Story -

0

1 2 9

2 5 8

3 8 7

5 1 6

U

S

33 n/a

34 n/a

35 n/a

36 n/a

37 n/a

38 n/a



38 n/a

39 n/a

40 n/a

41 n/a

42 n/a43 n/a

44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a







P 0 - 0.0 h

F 0 - 0.0 h

S 0 0 0 h

14 - X

P

F

B

U



S 0 - 0.0 h

B 0 - 0.0 h


Test

Result

Date

Tested Tester

TC

Time

Comment /


1 n/a

2 n/a

3 n/a

4 n/a

5 n/a

6 n/a

7 n/a

8 n/a

9 n/a10 n/a

11 n/a

12 n/a

13 n/a

14 n/a

15 n/a

16 n/a

17 n/a

18 n/a

19 n/a

20 n/a

21 n/a

22 n/a

23 n/a

24 n/a

25 n/a

26 n/a

27 n/a

28 n/a

29 n/a

30 n/a31 n/a

32 n/a

User Story -

0

1 2 9

2 5 8

3 8 7

5 1 6 S

33 n/a

34 n/a

35 n/a

36 n/a

37 n/a

38 n/a



39 n/a

40 n/a

41 n/a

42 n/a43 n/a

44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a








33 n/a

34 n/a

35 n/a

36 n/a

37 n/a

38 n/a

39 n/a



39 n/a

40 n/a

41 n/a

42 n/a43 n/a

44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a







P 0 - 0.0 h

F 0 - 0.0 h

S 0 - 0.0 h

B 0 0 0 h

16 - X

02

95

88

71

6

P

F

B

U

S



B 0 - 0.0 h


Test

Result

Date

Tested Tester

TC

Time

Comment /


1 n/a

2 n/a

3 n/a

4 n/a

5 n/a

6 n/a

7 n/a

8 n/a

9 n/a10 n/a

11 n/a

12 n/a

13 n/a

14 n/a

15 n/a

16 n/a

17 n/a

18 n/a

19 n/a

20 n/a21 n/a

22 n/a

23 n/a

24 n/a

25 n/a

26 n/a

27 n/a

28 n/a

29 n/a

30 n/a31 n/a

32 n/a

User Story -

1 2

2 5

3 8

5

33 n/a

34 n/a

35 n/a

36 n/a

37 n/a

38 n/a

39 n/a

40



40 n/a

41 n/a

42 n/a43 n/a

44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a








33 n/a

34 n/a

35 n/a

36 n/a

37 n/a

38 n/a

39 n/a

40 n/a



40 n/a

41 n/a

42n/a43 n/a

44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a







P 0 - 0.0 h

F 0 - 0.0 h

S 0 - 0.0 h

B 0 - 0.0 h

18 - X

0

1 2 9

2 5 8

3 8 7

5 1 6

P

F

B

U

S




Test

Result

Date

Tested Tester

TC

Time

Comment /


1 n/a

2 n/a

3 n/a

4 n/a

5 n/a

6 n/a

7 n/a

8 n/a

9 n/a

10 n/a

11 n/a

12 n/a

13 n/a

14 n/a

15 n/a

16 n/a

17 n/a

18 n/a

19 n/a

20 n/a21 n/a

22 n/a

23 n/a

24 n/a

25 n/a

26 n/a

27 n/a

28 n/a

29 n/a

30 n/a31 n/a

32 n/a

User Story -

33 n/a

34 n/a

35 n/a

36 n/a

37 n/a

38 n/a

39 n/a

40 n/a



41 n/a

42 n/a

43 n/a

44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a







P 0 - 0.0 h

F 0 - 0.0 h

S 0 - 0.0 h

B 0 - 0.0 h

T t D t TC C t /

19 - X

0

1 2 9

2 5 8

3 8 7

5 1 6

P

F

B

U

S




Test

Result

Date

Tested Tester

TC

Time

Comment /


1 n/a

2 n/a

3 n/a

4 n/a

5 n/a

6 n/a

7 n/a

8 n/a

9 n/a

10 n/a

11 n/a

12 n/a

13 n/a

14 n/a

15 n/a

16 n/a

17 n/a

18 n/a

19 n/a

20 n/a21 n/a

22 n/a

23 n/a

24 n/a

25 n/a

26 n/a

27 n/a

28 n/a

29 n/a

30 n/a

31 n/a

32 n/a

User Story -

33 n/a

34 n/a

35 n/a

36 n/a

37 n/a

38 n/a

39 n/a

40 n/a

41 n/a



41 n/a

42 n/a

43 n/a

44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a







P 0 - 0.0 h

F 0 - 0.0 h

S 0 - 0.0 h

B 0 - 0.0 h

Test Date TC Comment /

20 - X

0

1 2 9

2 5 8

3 8 7

5 1 6

P

F

B

U

S




Test

Result

Date

Tested Tester

TC

Time

Comment /


1 n/a

2 n/a

3 n/a

4 n/a

5 n/a

6 n/a

7 n/a

8 n/a

9 n/a

10 n/a

11 n/a

12 n/a

13 n/a

14 n/a

15 n/a

16 n/a

17 n/a

18 n/a

19 n/a

20 n/a21 n/a

22 n/a

23 n/a

24 n/a

25 n/a

26 n/a

27 n/a

28 n/a

29 n/a

30 n/a

31 n/a

32 n/a

User Story -

33 n/a

34 n/a

35 n/a

36 n/a

37 n/a

38 n/a

39 n/a

40 n/a

41 n/a

42



42 n/a

43 n/a44 n/a

45 n/a

46 n/a

47 n/a

48 n/a

49 n/a

50 n/a






Documents

Testing Scenarios