Test case example - Software Testing. Anybody can write test cases but not all can write test cases that are effective. A good test case is one which has higher probability of finding defect(s) that are not already discovered. Writing good test cases is very important for Testing to be successful.
Wikipedia:Template sandbox and test cases. and makes it easier to maintain test case pages. These templates include. Examples Basic format Template. Test Case ID: Test Items Describe features and conditions tested Input Specifications Data Names Ordering. Test Case Templates Author: Rex Black Last modified by.
7/28/13. Sample Test Case Template with Examples [Download] — Software Testing Help Software Testing Help Software Testing Complete Guide Search. Choose from an array of free or paid test case templates that are fully customizable according to your needs. 3 Sample Likert Scale Templates & Examples to Download. Test Case Template and Examples. Test Case #: 2.2 Test Case Name: Change PIN Page: 1 of 1 System: ATM Subsystem: PIN Designed by: ABC. Test case example. April 20th, 2010 | functional testing, manual testing. good article on Test Case and examples on Test Cases #4 明 on 04.06.12 at 1:40 pm.
Below are some of the points to be kept in mind while creating Test Cases. Understand requirements thoroughly. First understand Business requirements get the big picture of what is being achieved from business perspective. Read and understand how Business requirements are exploded into functional requirements. Go through Technical specification and UI design document to gain understanding of how the business requirements get translated into application functionality.
Once you do this exercise obviously you will get at least few questions or you may even discover few gaps in the requirements. Reach out to Business Analyst and Business User (as required) and get your questions answered. Now you are ready to go ahead with your Test Scenario identification.
Title: Test Case Template Subject: Author: Daniel Vitek MBA, PMP - Consultant to CDC NCPHI Keywords: CDC Unified Process, CDC UP, CDCUP Description. Sample Test Case Template with Examples. Test-case -example.jpg. 28. This. i need any Sample test case template and tell me How to write test cases for business. TEST CASE Fundamentals. DEFINITION. A test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies.
Identify Test Scenarios, Test Conditions and Expected results. Once you have sign- off on Test Scenarios, Test Conditions and Expected results, start creating Test Cases. Referring to Design documents is a must.
Writing test case to cover requirements is not just good enough; one should also consider verifying the technical aspects mentioned in the Technical and look and feel aspects mentioned in UI design documents. Some of the technical aspects like Field Length, validation, data structures will be documented in- detail in Technical specification.
So, during test case construction, one has to incorporate additional validations as well. Get your Test Cases reviewed by Business Analyst and Business Users. It is always good to get inputs from SMEs (Subject Matter Experts).
It is better to get review comments from Business Analysts and Business Users before testing starts rather than they pointing out at the deficiencies of your test cases during UAT or Post implementation. Test Cases steps should be as detailed as possible and should not be written at high level. Writing detailed test steps is very important considering the fact that the same person who wrote the test cases may not always execute the same test cases.
If the test cases are not very detailed then the person who executes the test case for the first time will not be able to validate the system thoroughly as he/she might have not gone through the requirements and will test only as per the test case steps. Example of a Test Case that is written at high level. Step No: 1. Step Description: Login to test application with valid user id/password. Expected Result: Home page is displayed. Step No: 2. Step Description: Click “Logout” link on home page. Expected Result: Login page is displayed. Example of a Test case written that is written in detail.
Step No: 1. Step Description: Open URL https: //www. Expected Result: Login page is displayed and contain the below fieldsa) “User Name” text fieldb) “Password” text fieldc) “Submit” button. Step No: 2. Step Description: Once Login page is displayed. Enter valid userid/password. Enter “vijay” in “User Name” text fieldb) Enter “abc. Expected Result: a) Verify “User Name” is populated with text “vijay”b) Verify text entered in “password” field is masked and is not readable.
Step No: 3. Step Description: Click “Submit” button. Expected Result: Verify application “Home” page is displayeda) Verify “Home” page displays “Welcome Vijay” message on top of left navigation Menu. Verify Left Navigation menu contains links “Directory”, “Submission”, “Latest Links”, “Approve Links”, “Logout”. Step No: 4. Step Description: Click “Logout” link on the left menu. Expected Result: Verify user is successfully logged out of the application and application login page is displayed https: //www. Write test cases in simple plain English that can be understood by anybody who is reading it, do not try to use words or sentences that can lead to ambiguity. This point is very important as your test cases might be reviewed or executed by your counter parts who can be from a different country.
Remember, intelligence lies in making complicated things look simple and not in making simple things complicated. Requirement Traceability Matrix (RTM) should be created for every project / release and should be kept up to date at any given point of time. RTM is one document that helps to ensure all the requirements are covered i. Provide Test Data within the Test Cases. In order for the test case to be complete, Test data and other required information like URL, User id and passwords required for testing should be provided with in the test case. Test Cases need to be modularized.
Common steps like “Login”, “logout” and other application specific common steps can be documented as common steps and can be called within other test cases as required. As a result, the task of maintaining test cases will become easier. E. g.: - If you have 1.
Test cases and application URL has changed then imagine the time required for updating 1st step in all the 1. Common steps that is called in all the other 1. Some of the Test Management softwares like Quality Center provides this facility. Test Case version control is a must.
Its is very important to track changes made to test case(s) this is for ensuring deliberate or accidental deletion or updates to test cases are tracked. Always prioritize test cases.
Every test case should be updated to indicate its priority (Critical, High, Medium and Low). Assigning priority to test cases helps to quickly identifying test cases based on their importance during critical phases of the project (Risk Based testing approach). Categorizing and running test cases based on priority will result in identifying critical during early stages of Testing. Test Case should contain Pre- requisites and Clean up sections.
Pre- requisite is something that is required to be done or “to be ensured” before running the test case. Providing pre- requisites is very important as mentioned earlier, the person who creates the test case may not be the one who will actually execute them. E. g.: - Prerequisite for testing a web based application “A” can be, to be tested on I. E 6 browser or on higher version. Incase a person who is running the test case is not aware of this prerequisite, then he/she will run the test case in whatever browser /version available on his/her PC and may even log a defect not realizing that the defect could be invalid. Incase some cases not ensuring pre- requisite conditions can lead to slippage of defects i.
Cleanup section is very important in some test cases that involve configuration or database changes. E. g.: - Tester “X” changes application configuration and does not revert back the changes (i. Tester “Y” runs his test cases may find issues or defects due to configuration changes done by Tester “X”. Not having cleanup steps or not running clean up steps can result in logging invalid defects, which is not desirable by developers, management or you.
Other Interesting Articles.