Upload
oana-feidi
View
831
Download
2
Embed Size (px)
DESCRIPTION
Citation preview
SOFTWARE QUALITY ASSURANCETEST CASE
Seminar: Oana FEIDIQuality Manager – Continental Automotive
Test case vs Scenario
A set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement
a test case must be reasonably capable of revealing information
Scenario – it is a general description of a particular requirement/functionality
Test case – it is the interpretation of the scenario with actual data
Scenario - Example
Identifier
Scenario01
Conditions satisfied
BA 9
Scenario description
Run the application so that the UI panel appears.
Enter invalid values like non integers, chars or strings for a, b and c respectively.
Click "Verifica".
Output
The following error message is displayed, written in red italic:
"Valorile date nu se incadreaza in intervalul specificat."
no specific values for input data
TRACEABILITY!
Test case structure - Information Information contains general information about Test
case. Identifier is unique identifier of test case for further
references, for example, while describing found defect. Test case owner/creator is name of tester or test
designer, who created test or is responsible for its development
Version of current Test case definition Name of test case should be human-oriented title which
allows to quickly understand test case purpose and scope.
Identifier of requirement which is covered by test case. Purpose contains short description of test purpose,
what functionality it checks. Dependencies
Test case structure - Activity Testing environment/configuration contains
information about configuration of hardware or software which must be met while executing test case
Initialization describes actions, which must be performed before test case execution is started. For example, we should open some file.
Finalization describes actions to be done after test case is performed. For example if test case crashes database, tester should restore it before other test cases will be performed.
Actions step by step to be done to complete test. Input data description
Test case structure - Results Expected results contains description of what
tester should see after all test steps has been completed
Actual results contains a brief description of what the tester saw after the test steps has been completed. This is often replaced with a Pass/Fail. Quite often if a test case fails, reference to the defect involved should be listed in this column.
Actual results field will be filled in after running the test case
Test case structure - ExampleIdentifier Test001
Test case creator Oana FEIDI
Version 0.1
Name of test case Verify that an error message appears when entering invalid values
Identifier of requirement -
Purpose To verify that an error message appears when entering invalid values, such as non-integers, chars or strings.
Dependencies None
Test environment Java 1.5.0 installed on the PC
Initialization Run the program so that the UI panel appears
Finalization Close the UI panel
Actions In the UI panel enter the following data, in the corresponding field:
a = 99, b = 1, c = !a# c
Click "Verifica" button.
Input data a = 99, b = 1, c = !a# c
Expected result The following error message is displayed, written in red italic:
"Valorile date nu se incadreaza in intervalul specificat."
TRACEABILITY!!!!!
Exercise
Create test cases for solving the following equation: a * x * x + b * x + c = 0 a, b, c real numbers [-150, 10]
The following are displayed in a pop-up x1, x2 the numbers
If the selected numbers are not part of the interval the following error message is displayed
"Error: invalid values.“ If a=0, the following error message will be displayed: “Not a
quadratic equation. The coefficient a can not be zero.”
Test it at the following link: http://id.mind.net/~zona/mmts/miscellaneousMath/
quadraticRealSolver/quadraticRealSolver.html
Test case
Start
Functional test development
Run tests
Test OK?
Coding
no
No more changes to TC
yes
Endyes
no
Start
Run tests
100% test completeness
criteria reached?
Add missing test cases
no
End
yes
Coding
We need a combination between structural and functional