TCM Lite

Release #XX
Project: #123456 Enter project name TCM Lite
Current Test Cycle Snapshot

Company Information
Attribute Company Division / Dept Street Address City, State Value Enter company name Enter department Enter street address Enter city and state
Test Cycle Information

Attribute Test Cycle Name Test Cycle Type Release Date Project Manager Business Analyst QA Tester QA Tester QA Tester QA Tester Value Release #XX Enter test cycle type Enter release date ? ? ? ? ? ?
Project Information
Attribute Project Number Project Name Value #123456 Enter project name
Test Areas (Worksheet /Tab Names)

Test Area 1-A 2-X 3-X 4-X 5-X 6-X 7-X 8-X 9-X 10 - X 11 - X 12 - X 13 - X 14 - X 15 - X 16 - X 17 - X 18 - X 19 - X 20 - X Total 11
1.5 h
Test Results Graphs

TC Count 8 7 6 5 4 3 2 1 0
1
Who Terry
TC Test Count Time 1.5 h 11
Test Time 1.0 h 0.8 h 0.6 h 0.4 h 0.2 h 0.0 h
Test Results Table

Test Result Status Untested Passed Failed Skipped Blocked Total N/A TC % Test Count Count Time 0.0 h 7 64% 1 1 1 1 11 989 9% 9% 9% 9% 100%
0.3 h 0.8 h 0.0 h 0.4 h 1.5 h 0.0 h
XL Template by:
mplate by:
Release #XX
Project: #123456 Enter project name TCM Lite
Past Test Cycles Trend

Total Test Case Counts
600 500 400 300 200 100 0 1 2 3 4 5 6 7 8 9 10 60.0 h 40.0 h 20.0 h 0.0 h 1 1 2 3 4 5 6 7 8 9 10 2 3 4 5 6 7 8 9 10 120.0 h 100.0 h 80.0 h
Total Test Time
Test Cycle
Failed Test Case Counts

30 25 20 15 10 5 0
Test Cycle
Test Cycle
Test Cycle Test Results

Test Cycle Name Beta 1.00 Release RTM 1.00 Release RTM 1.01 Release RTM 1.02 Release RTM 1.03 Release RTM 1.10 Release RTM 1.11 Release Beta 2.00 Release RTM 2.00 Release Test Case Counts
Total Failed
# 1 2 3 4 5 6 7 8 9
Total Test Time 40.4 h 111.3 h 90.8 h 92.3 h 75.8 h 85.4 h 76.4 h 65.2 h 66.4 h 61.8 h
XL Template by:
109 356 379 412 439 504 514 519 543 552
15 24 16 14 13 12 4 4 3 2
10 RTM 2.01 Release
mplate by:
Instructions
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, XL supports 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 - Quick Start Guide 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:
text text text Title Title Title
Type your project data into the white cells Type section header names into the blue cells Do not type over gray cells, especially those with formulas Do not type over dark gray column title cells Do not type over black title cells Do not alter graphs, they will automatically re-calculate and re-size as needed
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 - Clearing Sample Data from Template:

When you first receive this template, it is filled with sample data to demonstrate usage. You will need to clear out this sample data before you start using it for your projects. Here is a quick list of what to clean: Summary Worksheet: Clear out white cell values in sections: "Company Information", "Project Information", "Test Cycle Information", and "Test Areas". Leave gray cells along because they are formulas. Test Case Worksheets (1 - A, 4 - X, etc.): Clear out white cell values in columns "Test Steps", "Expected Results", "Date Tested", "Tester", "Comments" Note that you cannot simply clear out column (Status); but instead must use search & replace to default the cell values to either U (untested) or n/a (not applicable). See the section "1.3 - Reset Test Case Execution Status for New Test Cycle"
1.3 - Reset Test Case Execution Status for a New Test Cycle:
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. 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. A 1 B
2. Repeat Search and Replace for the letters 'F', 'B', and 'S' also, changing them back to 'U' for the next test cycle.
1.4 - Multi-User Shared Mode:

Often, there is more than one tester working a given project. It is thus crucial to share the project test case spreadsheet out 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: 1. Select Tools >> Share Workbook from XL's menu (see [A] below): A
2. Be sure "Allow changes by more than one user at a time" is checked (see [B] below) B
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).
B A
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 meetings or to update management on the current test-cycle status. B A
2.A - Company Logo:

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.
2.B - Report Title: Test Cycle Name + Project Number & Project Name:
Do not type over this text; it is automatically pulled from 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).
2.C - Company Information:

Enter Company Information such as the company's name, address, or your division into the white cells.
2.D - Project Information:

Enter Project Information such as the project's number and name into the white cells. Note that these values are automatically used in the report headers of the "Snapshot" and "Trend" worksheets.
2.E - Test Cycle Information:

Enter Test-Cycle information into the white cells. Test cycles represent a run of all test cases; for example if you are following a scrum model, then you might be running all test cases once per sprint as a regression check. In this case, your Test-Cycle name would be the sprint name or sprint number. The release date represents the current Test-Cycle deadline. Regarding the attribute names, note that some of the cells are white (change-able) and not the typical gray (don't change). This is implies that you can change the staff type in the white cells below to match your company's job names, and your project's job type composition.
2.F - Test Areas:

You break down your test areas in two ways: (1) by Test Area in separate worksheets like "1 - A", or "3 - X" which you rename to match your project needs, and (2) by blue highlight rows (User Stories) to group similar test cases within a Test Area worksheet. This section of the Snapshot report quickly summarize each Test Area (worksheet tab) by name, test case count, the tester responsible for executing tests, and the current actual (done) + estimated (not yet done) test times. Test Area: Do not change these values; the formulas will automatically populate the cells based on the corresponding worksheet tab names. Instead, change the worksheet tab names to represent your test areas. Note: press F9 for XL to recalculate if this column's values are ever blank. Who: Enter the QA Tester responsible for the test area / worksheet Test Case Count: Total test case count for the test area / worksheet. Do not type over the formula. Test Time Total "test time" for this test area \ worksheet. Note: "Test time" includes time to research, write, and execute the test case. The first test cycle for a test case is large; subsequent test cycles will be much smaller because there will only be execution time.
2.G - Test Result Graphs:

These two simple bar charts depict the test case counts and test case time, grouped by test result status. Test Case Count: This graph shows the total count of test cases, across all test area / worksheets; grouped by test result type (Pass, Untested, etc.). Use this graph to quickly scope remaining work (untested + blocked + failed test case count), or see how far along you are (passed) Test Time: This graph shows the total test time (research, write-up, and execution times) grouped by test result type. Use this to determine how much time has been spent already (passed, skipped, failed) and how much time remains (blocked, untested)
2.H - Test Result Table:

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 much time remains to completion.
3 - Past Test Cycles Trend 3.1 - Worksheet Definition:

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. A B
3.A - Company Logo:

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.
3.B - Report Title: Test Cycle Name + Project Number & Project Name:
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:

This graph depicts the total test case count over time. It represents test case coverage.
3.D - Failed Test Case Count Graph:

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:

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.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 gray rows starting at the tip of the blue arrow and blue text located at the bottom of the table (see [G]), right-click and select "insert copied cell."
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
H D E F G
4.A - Test Area (Worksheet Title):

This black bar contains the name of the Test Area which logically groups all test cases on this page. Do not type over the formula in this cell; instead double-click the worksheet tab name and change it there (item [M]). The black bar test area title will automatically change to match the tab name.
4.B - Test Results Graph:

As you enter test results (pass, fail, etc.) on the worksheet, this graph will automatically adjust to reflect the changing status. Use this graph to quickly check how many untested cases remain, how many failed cases (bugs) are in this test area, etc. The data for this graph is pulled from the Test Case Results table to the right (item [C]).
4.C - Test Results Table:

As you enter test results (pass, fail, etc.) on the worksheet, this table will automatically adjust to reflect the changing status. This table feeds the Test Results graph on the left.
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:

Type-over sample test steps 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:

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:

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: White background = Done (Pass, n/a, and Skip) Red background = Fail Yellow background = Blocked Light yellow background = Untested Two ways to enter a status value: Hover mousepointer and use the drop down Key in P, F, S, B, U, or n/a 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: 1. Press ctrl-; to insert today's date 2. Copy and paste from above as you test
4.I - Tester Column:

Enter your name (or name of the QA Tester) who executed the test case.
4.J - Test Time Column:

Total estimated research, write-up, and execution time for this test case, in the current test cycle on. Update with actuals after you run the test. Typically, you can use "1m" for simple tests, and "3m" or "5m" up to "90m" for more involved tests. If you have really fast test cases, then put "1m" at the top of the user story / use case section, and "0m" for the remaining test cases in that section.
4.K - Comments Column:

Key in any comments that may clarify the test case Optionally use this as a tracability matrix by adding text like "xref.Req.143.23" Optionally add Roles or other helpful text
4.L - Bookmark Column:

Enter X's on rows that you want to quickly jump to such as Status = F or B 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.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: 1. Highlight an empty source row:
2. Press ctrl-C to copy the highlighted row 3. 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. 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:
5. 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 - Managing Test Cases 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 and functionality of the app to define your Test Areas (spreadsheet tabs) TCMLite ships with a standard default layout with placeholders "3 - X", "4 - X", etc. You should rename these to fit your needs.
5.2 - Test Case Writing Guidelines:

DO's when writing test cases DO Have one "Verify" statement per test case row (in the expected result column). DO Write each case to be executed standalone. It shouldnt depend on other test cases (as much as possible). DO Break down the app and write steps to the functionality. This eliminates constant rework of the test cases when code changes. DO think re-usable scripts when writing your test cases. DO keep an eye out for writing steps in such a way that they can be automated in the near future. Do NOTs When Writing Test Cases: DO NOT use the words "correctly", "as it should", "properly" or other value statements. Define the expected behavior.
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. 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.
WinTestGear - TCM Lite Version 1.0.3 Copyright 2010 "TCM Lite" is a freeware product; free to use and free to distribute!
Please forward bugs or product enhancement suggestions to:

mailto:tcmlite@wintestgear.com http://www.wintestgear.com
Legal Disclaimer
THE SOFTWARE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND WHETHER EXPRESSED OR IMPLIED. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, WINTESTGEAR FURTHER DISCLAIMS ALL WARRANTIES, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. THE ENTIRE RISK ARISING OUT OF THE USE OR PERFORMANCE OF THE PRODUCT AND DOCUMENTATION REMAINS WITH RECIPIENT. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL WINTESTGEAR BE LIABLE FOR ANY CONSEQUENTIAL, INCIDENTAL, DIRECT, INDIRECT, SPECIAL, PUNITIVE, OR OTHER DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR OTHER PECUNIARY LOSS) ARISING OUT OF THIS AGREEMENT OR THE USE OF OR INABILITY TO USE THE PRODUCT, EVEN IF WINTESTGEAR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no event shall the author be held liable for any damages whatsoever, including without limitation, damages for loss of business profits, business interruption, loss of business information, or any other loss arising from the use or inability to use the software.
1-A
P F B U
10 12 0 2 4 6 8
Test Case Results

U P F S B 7 1 1 1 1 64% 9% 9% 9% 9% 0.0 h 0.3 h 0.8 h 0.0 h 0.4 h
TC# Test Execution Steps User Story 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
Expected Result
Test Result P F S B U U U U U U U n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a
Date Tested
Tester
TC Time 15 m 50 m 1m 25 m
Comment / (or Requirement xref)
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a Copy test case rows and insert-paste here to shift down the gray lines and preserve the automatic calculations.
2-X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Test Result n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
3-X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
4-X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
5-X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
6-X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
7-X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
8-X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
9-X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
10 - X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
11 - X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
12 - X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
13 - X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
14 - X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
15 - X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
16 - X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
17 - X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
18 - X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
19 - X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
20 - X
P F B U
0.3129 0.6258 0.9387 1.2516 0
Test Case Results

U P F S B 0 0 0 0 0 0.0 h 0.0 h 0.0 h 0.0 h 0.0 h
Expected Result
Date Tested
Tester
TC Time
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50

TCM Lite

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

TCM Lite

Încărcat de

Drepturi de autor:

Formate disponibile

Release #XX

Project: #123456 Enter project name TCM Lite

Current Test Cycle Snapshot

Test Cycle Information

Test Areas (Worksheet /Tab Names)

Test Results Graphs

TC Test Count Time 1.5 h 11

Test Time 1.0 h 0.8 h 0.6 h 0.4 h 0.2 h 0.0 h

Test Results Table

Past Test Cycles Trend

Total Test Time

Failed Test Case Counts

Test Cycle Test Results

10 RTM 2.01 Release

1 - Quick Start Guide 1.1 - General Data Entry Rules:

1.2 - Clearing Sample Data from Template:

1.4 - Multi-User Shared Mode:

1.5 - Context-Sensitive Help:

2 - Current Test Cycle Snapshot 2.1 - Worksheet Definition:

2.A - Company Logo:

2.C - Company Information:

2.D - Project Information:

2.E - Test Cycle Information:

2.F - Test Areas:

2.G - Test Result Graphs:

2.H - Test Result Table:

3 - Past Test Cycles Trend 3.1 - Worksheet Definition:

3.A - Company Logo:

3.C - Total Test Case Count Graph:

3.D - Failed Test Case Count Graph:

3.E - Total Test Time:

3.F - Test Cycle Test Results:

4 - Test Case / Test Area Worksheets 4.1 - Worksheet Definition:

4.A - Test Area (Worksheet Title):

4.B - Test Results Graph:

4.C - Test Results Table:

4.D - Test Case Number Column:

4.E - Test Execution Steps Column:

4.F - Expected Result Column:

4.G - Test Result Column:

4.H - Date Tested Column:

4.I - Tester Column:

4.J - Test Time Column:

4.K - Comments Column:

4.L - Bookmark Column:

4.2 - Copy-Inserting New Test Case Rows:

5 - Managing Test Cases 5.1 - Organizing Test Cases:

5.2 - Test Case Writing Guidelines:

Please forward bugs or product enhancement suggestions to:

Test Case Results

TC# Test Execution Steps User Story 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

Comment / (or Requirement xref)

Test Case Results

TC# Test Execution Steps User Story 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

Comment / (or Requirement xref)

Test Case Results

TC# Test Execution Steps User Story 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

Comment / (or Requirement xref)

Test Case Results

TC# Test Execution Steps User Story 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

Comment / (or Requirement xref)

Test Case Results

TC# Test Execution Steps User Story 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32