SQUASH. Quick Start Guide for Squash TM V1.2.0.RELEASE SUMMARY

Transcription

1 SQUASH Quick Start Guide for Squash TM V1.2.0.RELEASE SUMMARY 1 SQUASH TM : GENERAL CONCEPTS PROJECT CREATION AND CLEARANCES MANAGEMENT REQUIREMENT MANAGEMENT... 5 MODUS OPERANDI... 5 GOOD PRACTICE TEST CASE MANAGEMENT... 6 MODUS OPERANDI... 6 GOOD PRACTICE... 6 MODUS OPERANDI... 7 MODUS OPERANDI... 8 REPORT ON REQUIREMENT COVERAGE BY TEST CASES CAMPAIGNS AND ITERATIONS MANAGEMENT MODUS OPERANDI GOOD PRACTICE MODUS OPERANDI MODUS OPERANDI GOOD PRATICE RULE MODUS OPERANDI TEST CASE EXECUTION MODUS OPERANDI EXECUTION PROGRESS REPORT REPORTING REQUIREMENTS COVERAGE BY TESTS REPORT TESTS EXECUTION PROGRESS REPORT /21

2 1 SQUASH TM : GENERAL CONCEPTS SQUASH TM (Test Management) is a software testing management tool. It is an operational platform for test repository, structured in different «SPACES», each representing a major concept in the testing lifecycle. At the top level, the project space is mainly devoted to data from software or a system under test. To the project space are teamed up secondary components which are described below: Requirement space Test Case space Campaign and iteration space Reporting space (advancement and functional coverage). In the following figures, you can notice the space organization and which roles are associated to each space: Functional Users specifications Reports 3 Profile groups Administrator Project Manager User Project Requirement Verified by 2 Reports Requirement coverage by test cases Execution progression Test Case associated to Run in Campaigns Carried out in Iterations 2/21

3 SQUASH TM offers a test process in which each concept or Space answers for a specific need: Requirement Space: allows referencing of technical and functional requirements extracted from the software specifications. Test cases Space: allows specifying test cases (creation, definition and test referencing) from software specifications. Campaigns and iterations Space: allows campaign execution planning and the automatic or manual execution of test cases. Reporting Space: Reporting on execution advancement and functional coverage. The following figure represents each space included in the global process: 3/21

4 2 PROJECT CREATION AND CLEARANCES MANAGEMENT The first step to start using Squash TM is to ask the administrator to: To create one or several projects if none exists, To assign clearances on the required project. A project must be dedicated to: A software application Or process operation (based on several software applications) 4/21

5 3 REQUIREMENT MANAGEMENT Requirements are extracted from Functional specifications and assigned to a special version of the system under test. The creation of requirements is accessible through the requirement space and is the first step in testing a project. This feature is accessible for users with the right clearances on the project. MODUS OPERANDI Click on the requirement space button. Select an existing project. Click on the [Add] button located at the top of the tree menu and select «New requirement». A pop-up window must appear. You may complete the required fields. Click on the [Add] button. The new requirement will be added in alphabetic order to the requirement list of the selected project. Attention: An [F5] is necessary to refresh the page. GOOD PRACTICE The folder represents one or multiple functional modules. The software version must be noted in the requirement reference Requirement naming convention: <RequirementNumber>-<FunctionalModule>-<ApplicativeVersion Example : E0001-admin-v /21

6 4 TEST CASE MANAGEMENT Test case creation is happens in the Test case Space. The process is similar to requirement creation. This feature is available for users with the right clearances on the active project. MODUS OPERANDI Test case creation: Go to the «Test case Space», by clicking on Select an existing project. Click on the [Add] button located at the top of the menu tree and select «New test case». A pop-up window must appear. You may complete the required fields. Click the [Add] button. The new test case will be added in alphabetic order to the test cases list of the selected project. Attention: An [F5 is necessary to refresh the page] GOOD PRACTICE The folder represents one or multiple functional modules. Test case naming rules: <Case type>-<testcasenumber>-<keyword> <Case type> : CAP = valid case, CNP = invalid case, CAL = border case Example of keyword : CAP0004- Inscription via form 6/21

7 MODUS OPERANDI Test step Creation: Select the test case in the project tree. In the «Script» Tab Table, click on the [Add a step] button. A pop-up window must appear. Then you may complete the required fields. Click on the [Add] and the Script tab is updated with the step you have just created. Good practice: A test case must call to a maximum of 2 others test cases. Example: Test case CAP0002-inscription updates which calls the step «1» of the test case CAP edition acceptance list. 7/21

8 MODUS OPERANDI To associate a test case to a requirement: Click on the [Associate Requirements] button from the retractable box «requirements verified by this Test Case». A secondary screen opens up including on the righ pane, a table titled «requirements verified by this Test Case» and on the left the project tree. Select the requirements to link up. Single or multiple selections are available. Click on the [>>] button, and the selected requirements will appear in the table on the right. Clicking this button [<<] will remove the requirements from any associations. Click on the [Return] button in order to go back the previous screen. The selected requirements will appear in the «requirements verified by this Test Case» retractable box. Focus: Test case requirement link: A test case can be linked up to one or several requirements. Nota Bene: It is also possible to link up a requirement to one or several test cases from the Requirement Space. To do this, you may observe the same procedure as explained above. 8/21

9 REPORT ON REQUIREMENT COVERAGE BY TEST CASES Reporting space is accessible through the navigation bar and leads to reports on requirement coverage by test cases. You may customize the report by selecting: a project type or one or several requirements versions. Select the «Report Space». Click on «requirement coverage by test cases (Progress follow up)». A «report criterias» retractable box must appear. Customize your report as you wish with the available attributes. Click on the [Generate] button. A page must appear showing the generated tables for the selected reports (Requirement coverage table, requirement by projects list). 9/21

10 5 CAMPAIGNS AND ITERATIONS MANAGEMENT In order to execute the test cases created above, it is necessary to create a campaign and then one or several iteration(s). This feature is available for a user profile with the required clearances. MODUS OPERANDI Test campaign creation: Go to the «Campaign Space» clicking on the button. Focus: Select the project you have first created. Click on the [Add] button placed above the campaign tree and select «New Campaign». A pop up window must appear. Then complete the required fields. Click the [Add] button. The new campaign will appear in the tree below the objects previously created in the tree. To be noticed: in order to rearrange campaigns in alphabetical order, you must refresh the page by clicking on the [F5] button of your keyboard. It is customary to create a campaign for each applicative version or each patch. A campaign gathers all the test cases necessary to qualify an applicative version or a business process. Each test strategy must describe a test perimeter. Create as much as iteration as described in the test strategy. 10/21

11 GOOD PRACTICE The name of the applicative version must be mentioned in the campaign keywords. Campaign naming charter: <Project label>-<applicative version> Key words Example : e-form-v /21

12 MODUS OPERANDI Adding a test case to a campaign: - Select the campaign you have previously created in the tree. In the «Test Plan» tab, click on the [Add] button. A page must open up in which you may select one by one or simultaneously all the tests you need to add. Click on these button [>>], [<<] for respectively add or remove a test case from the campaign. Click on the [Return] button in order to go back to the previous view and to check all the test cases added to the «test plan» tab table. 12/21

13 MODUS OPERANDI Iteration creation: Select the campaign you have previously created. Click on the [Add] located at the top of the tree and select «New iteration». A pop-up window must appear. You may complete the required fields. Click the [Add] button. The new iteration will be placed on the tree below the objects previously created in the tree. To be noticed: in order to classify the iteration in the alphabetical order you must refresh the page by clicking the [F5] on your keyboard. Upon the creation of a new iteration, all test cases previously associated to the campaign will be added to the selected iteration test plan tab. GOOD PRATICE RULE Iteration naming charter: IT<IterationNumber> Keyword example : IT01 13/21

14 MODUS OPERANDI Test suite creation: Select iteration from the project tree. Click on the [Test Suites] button located on the right pane of the iteration page A pop-up window must appear. You may complete the required fields then click on the [Add] button. Click on the [Close] button. Upon the creation of a test suite, it will be added to the tree at the following of the iteration. 14/21

15 To link up a test case to a test suite: Select in the «Test Plan» tab table all the test cases that you want to add to the test suite. Click [Test Suite] located above the table of the «Plan test» tab of the iteration. A pop-up window must appear, select your test suite in the existing test suite lists. Click on the button. All test cases selected during the previous step must be added to the test suite. Focus: The test suite functionality allows you to run all test cases contained in the test plan in an assembly line. You also may execute your test one by one as explained below.. 15/21

16 6 TEST CASE EXECUTION This feature requires adequate clearances on a selected project. MODUS OPERANDI 16/21

17 Select an iteration previously created within a campaign. You may specify the user who will execute the test case. Click on the test case name in the table of the «Test Plan» tab in the iteration page. Then click on the link New execution. A secondary page must appear. Click on the [run with IEO] or [Execute]. button A pop-up must appear showing the first step of the test case to be executed. Upon the end of the execution the user may choose several options: Click on [Failure] or [Success] Ready Or choose to use the combo box shown on the right. Block Failure Success Finally, the status of the test case under execution is updated. Focus: When the user clicks on [Failure] or [Success] The execution of the next test case launches automatically Or a pop-up window informs you of the end of the execution, if the user was on the last step. When the user chooses the step status from the combo box (), the user must pass to the next step manually using the button located to the left or the right of the step number (). 17/21

18 EXECUTION PROGRESS REPORT Users can access to the Report Space from the navigation bar. This space contains the execution progress report. You may customize your report by choosing criterias such as campaign status or several campaigns. Select «Report space». Click on «Execution Progress (Progress Follow up)» In the workspace, a retractable block must appear titled «Criteria of the report». Select the attributes you want to generate. Click on [Generate]. A new page opens up showing the table of the generated report (The campaign progress dashboard and the list of test cases by campaign). 18/21

19 REPORTING Users can access several reports from the Report Space: Execution Progress Report, Requirement Coverage by tests Report REQUIREMENTS COVERAGE BY TESTS REPORT The process to generate this report is described on page 11 from the Test Case management Chapter. Select the tab «Table of requirements coverage» in order to obtain the list of all requirements coverage by tests and by project. Click on the menu bar «Export as» to choose the PDF or HTML format to export the report. 19/21

20 Select the«requirement list by project tab» to obtain the coverage for each requirement and the linked tests for a given project. Click on the menu bar «Export as» to choose the format: xls, ods, csv, pdf, html. TESTS EXECUTION PROGRESS REPORT The process to generate this report is described on page 21 of the Test case execution Chapter. Select the «Campaign follow-up Dashboard tab» to obtain the list of the execution progress by campaign and by project. Click on the menu bar «Export as» to choose the format for the export: pdf or html. 20/21

21 Select the «Test case list by campaign»tab to obtain the detailed progress of each test case by iteration, by campaign and by project and also the coverage of each test case linked up with a requirement within a project. Click on the menu bar «Export as» to choose the export format: xls, ods, csv, pdf, html. 21/21