08-16-2017, 10:24 PM
sample test cases for testing online ticket booking application
Test cases contains:
1. GUI testing
2. Navigation testing
3. Functional testing
4. Non functional testing (Performance Security)
5. Data validation testing
6. Negative testing
7. Data Base Testing
Test cases for Railway Registration:
1. Check whether there is a train for your destination.
2. Check the availability of seats on the required date.
3. Check whether the available seats for required coach that is A/c or Sleeper coaches.
Test Scenario: Train search with all route stations
1. Enter source and destination codes or source and destination corresponding trains are displaying or not
2. Enter train number and date source and destination with all stations are displaying or not
Scenario: check avaliablity of seats for required date
1. Search seats for Ac ,sleeper ,seat
2. Check upper middle ,lower births
3. Ticket fare for corresponding criteria
Booking :
Book the tickets with corresponding criteria
by cash or card
any concetion for senior citizen fi applicable
Scenario:
Print the ticket
same for cancelation of ticket
1. Check whether you have money.
2. Check the train is available & you have to go to the same destination.
3. Check working hrs of booking office
Step1: Verify there is a train available to the destination.
Step2: Verify the seats are available on the particular date.
Step3: Verify the seats available of the coaches like sitting or berth and check the fare of the particular system.
A car manufacturer does not produce car as a whole car. Each component of car is manufactured separately, like seats, steering, mirror, break, cable, engine, car frame, wheels etc.
After manufacturing each item, it is tested independently whether it is working the way it is supposed to work and that is called Unit testing.
Now, when each part is assembled with other part, that assembled combination is checked if assembling has not produced any side effect to the functionality of each component and whether both components are working together as expected and that is called integration testing.
Once all the parts are assembled and car is ready, it is not ready actually.
The whole car needs to be checked for different aspects as per the requirements defined like if car can be driven smoothly, breaks, gears and other functionality working properly, car does not show any sign of tiredness after being driven for 2500 miles continuously, color of car is generally accepted and liked, car can be driven on any kind of roads like smooth and rough, sloppy and straight etc and this whole effort of testing is called System testing and it has nothing to do with integration testing.
The example worked the way it was expected and client was convinced about efforts required for ST (system testing).