Test Harness

What is Test Harness?

Anybody have come across Test Harness. Well It is kind of code written in the form of WhiteBox Testing. In SDLC Model i.e V Model there is one Level for Testing called as Integration Testing where each modules are been broken into sub modules for testing and integrating components.
One Level in Integration Testing is System Integration Testing. Further in it there are different Strategies in it i.e Top Down approach and Bottom Up analysis.
Here in Top Down approach, Stubs are used and in Bottom Up analysis Drivers are used.
Stubs and Drivers are nothing but set of codes written unless the entire Code is not yet developed.
So if Developer has not yet completed his part of work these Stubs and Drivers are written in functions and procedures.
Hence this set of codes are called as Test Harness.

Tracebility Matrix in Software Testing

What exactly is Traceability Matrix?

First of all by name itself Trace gives the meaning that something has to be traced. Similarly for Software Testing everything has to be traced. In large projects each and every data has to be maintained for future reference. So there is a concept called Traceability Matrix.

So while preparing Traceability Matrix it can be done using Excel sheet or any other Test Management Tool  like Quality Center also. While preparing  Traceability Matrix in Excel these are the main things which need to be concentrated i.e,
Sample Template
Requirements ID  Req ID1.1  Req ID1.2  Req ID1.3  Req ID1.4  Req ID1.5 

Test Cases id
TC1.1
TC1.2
TC1.3
TC1.4
TC1.5

If a Tester leaves the organization and if he doesnot fill the report of   Traceability Matrix, how will the New Tester come to know what and all Test Cases have been written to which Requirement IDs.

So  Traceability Matrix  gives the entire coverage of How many Test Cases have been written, how many Test Cases executed, which defect has been raised on which Test Cases etc.

In Quality Center Test Coverage analysis prepares automatically all the reports and generates it after linkage is done by Testers of Test Cases to Requirements.   

Test Management Tool Quality Center

Quality Center is basically Test Management tool where you can manage your entire Test Data, Test Requirements, Test Cases in short all known as Test Deliverables.

Quality Center contains basically 4 Important Modules in it.

1. Requirements: Here all the Parent and Child requirements are written in Sequential order where every Parent and Child will be having their Unique Id no, which easily in future can be recognized if any changes of requirements will be done.

2. Test Plan: Here is the Module where entire Test Cases are managed in this Module along with Test Data also, apart from this these Test Cases are written in standard Template form. And entire Test Set are managed in this Module where even Export and Import of Excel or other files can be done in this Module. The Test Cases are linked to the Requirements module with their respective Ids.
The Template is i.e
Sl.No  Description   Expected Result  Actual Result  Status

3. Test Lab: Here is the Module where entire Test cases are executed after writing Test Cases it has to be executed so in this module we execute along with Test Data given in excel form. And further for executing the Test Cases it has to be linked to the Test Plan Module with their respective Ids.
Test suite is nothing but collection of Test Cases which can be executed.

4. Defects: Here is the module where entire Defects/Bugs are raised where each and every Bugs has Unique Id assigned to it. Defects can also be raised from test Lab if any execution fails at that time. 

Difference between Smoke Testing, Sanity Testing, Monkey Testing, Ad Hoc Testing

Few Difference between Smoke Testing, Sanity Testing, Monkey Testing, Ad Hoc Testing Concepts

Smoke Testing: This type of Testing is mainly done as the Checking of Basic Functionality when a Build is released and tried to test if Bugs are found in this test immediately Testing is stopped and does not go further for any different types of Testing. Mainly Positive Scenarios are tested

Sanity Testing: This type of Testing is also similar to Smoke Testing But here its type of Width wise Testing and for Checking of Basic Functionality when a Build is released and tried to test with Both Positive and Negative Scenarios if Bugs are found in this test immediately Testing is stopped and does not go further for any different types of Testing.   

Ad Hoc Testing: This type of Testing is done with No proper documentation or writing any Test Cases , here its just testing the application with no standard format.

Monkey Testing:  This type of Testing is done like for example if a Monkey uses some product or application how will he use it, similarly entering some Junk or Random Data in the fields and trying to test it.

Test Cases for Lift

Few Test Cases for Electronic Lift operation:

1. Test from Outside after pressing the button whether Lift Opens if it is in same floor.

2. Test from Outside whether Light is glowing or not, to know Lift is going up or down.

3. Test from Inside by pressing buttons at each floor.

4. Test all the buttons whether it is going to proper floor or not.

5. Test with Maximum Number of people inside the Lift i.e overloading of Lift.

6. Test the Lift when the Power suddenly goes Off and people are inside the Lift, an emergency button should be there for alarm.

7. Test for any wobbling inside the Lift.

8. Test for Lift within time limit it goes to each floor and does not cause delay.

9. Test for speed of Lift from Top floor to Bottom floor.

10. Test for Lift if suddenly in the Top something falls drastically and alarm should be ringed immediately.

11. Test for Lift properly whether it closes the door properly when button is pressed.

12. Test for Lift if number of people exceeds with Maximum weight in lift, Message or alarm should ring that Lift is overloaded.

13. Test for Lift from each floor the Lift opens at that floor and does not go to some other floor.

14. Test for Lift all the electronic buttons are working or not.

15. Test for Lift if suddenly some wire gets cut from Top some safety measures has to be initiated immediately.

Test Cases for Login scenarios

Few Test Cases for Login scenarios

1. Test for Valid Username and Password and click on Login, should successfully Login.

2. Test for entering Username and without Password and click on Login, should pop up message and ask for Password.

3.   Test for  entering Password and without Username and click on Login,  should pop up message and ask for Username.

4.   Test for InValid Username and InValid Password and click on Login,  should pop up message and ask for Valid Username first and then ask for Valid Password.  

5.   Test for Limited characters for  Username and Password and use Equivalence partitioning and boundary value analysis for both and click on Login

6.   Test for strong, weak password  with all wild characters in it and then click on Login.

7.   Test for password should be in encryption and should not be visible and click on Login

8.   Test for more security tags with html tags or sql injection in username and password so that no one hack the account.

9.   Test for forgot password if user is already registered and click on Login and email should be sent to User.

10.   Test for Change Password with Old Password should be different with New Password, should be able to change password successfully.

Test Cases for ATM Debit Card

Here are few scenarios for ATM Debit Card

1. Test the card with Valid ATM Card

2. Test the card with Invalid ATM Card

3. Test the card with proper Insertion of Card

4. Test the card with Direction facing the ATM Machine

5. Test the card  with insert and remove for certain Debit Card

6. Test the card which reads the Card from ATM Machine

7. Test the card when suddenly power is Off no information should be displayed and Card should be removed.

8. Test the card With No scratches on the Card.

9.  Test the card with proper valid PIN 

10. Test the card with Invalid PIN and deny operation if continuously Invalid PIN entered 

11. Test the card when entered  continuously Invalid PIN entered immediately message should be sent to Mobile. 

12. Test the Card with sensitivity of PIN entered in machine.

13. Test the Card with different Transactions displayed in Machine.

14. Test the Card with few transactions like Fast Cash, withdrawal, Current, Savings, Balance Inquiry etc.

15. Test the Card for entering Money with limited numbers not exceeding the limit.

16. Test the Card for entering Invalid numbers.

17. Test the Card when entered Valid PIN different transactions displayed.

18. Test the Card again if the middle of the transaction Card is inserted which it should stop transaction.

19. Test the Card with Valid account and Valid transaction of money and request for receipt.

20. Test the Card with in middle of transaction Power goes off and transaction should not deduct in account as money not yet received.

21. Test the Card with Mobile information with debit of money in the account.

22. Test the Card with Valid Savings or Current account type and request for receipt.

23. Test the Card with Invalid account type selected and deny the request for debit of money.

24. Test the Card with some untoward type of hacking/manipulation goes on from Account and immediately message should be sent to Owner and also for that particular machine owner.

25. Test for other types of devices used in ATM Machine.

26. Test the Card with No Money in the Account and request for receipt.

27. Test the Card when one transaction is over immediately it should be logged out of account.

28. Test the Card with minimum balance in account and entering More the balance so report an error.

29. Test the Card with an error should be displayed in Machine if No balance in Machine.

30. Test the Card with one transaction at a time.

31. Test the Card in Machine with Maximum withdrawal at a limit.

32. Test the Card with an Expiry Card

33. Test the Card with an machine where it swallows the Card.

34. Test the Card after Valid transaction Card should be reverted back to the owner if it is swollen machine.

35.Test the Card with Invalid transaction card with minimum number of times should be not reverted back and message sent to mobile.