Testing is Very Easy!

Everybody think like “testing is very easy”, “Valid and Invalid scenarios to test are very less”. Do you think it’s true?

Answer: No, it’s not true. 

If any Software Tester is in searching of the text “testing an application in easy ways”, then they are like a “Frog inside the Well”. [i.e., they end up with nothing.]

Every Software Tester;  

   ü  Should Think Out of the boundary. 

   ü  Should know the requirement thoroughly.

   ü  Should know the minor functionalities in an application.

   ü  Should think like a domain user.

   ü  Should feed the application with step by step attitude.

   ü  Should test lot of complex factors.

   ü  Should be thinking nerd and know the brain storming process.

   ü  Should educate the team, as well as the client.

   ü  Should be a usability guy. 

   ü  Should test the application as their friend.

   ü  Should not give chances to others, to identify the bugs. If others found, say congrats to them.

   ü  Should converse reasonably with others.

   ü  Should be a problem solver.

   ü  Should be a chameleon.

   ü  Should be proficient enough to test in any technology. 

   ü  Should be honest with bugs.

Software tester can test the program completely by trying all the possible inputs and states of a program or in detail cautiously.

“Good Test Suite = A Variety of Test Scenarios”

Consider an example for a login page:  A Software tester writes the test cases in distinct scenarios and they cover all the major functionalities. Herewith I am mentioning some of the possible scenarios that I have in my mind with regards to the three fields [Email ID (Text box), Password (Text box) and Login (Button)].

Validate whether the three fields are available.

Validate whether the valid users are logged in successfully.

Validate whether the valid user should be a registered user.

Validate whether the validation message is firing on blank submission.

Validate whether the validation message is fired for invalid “Email ID”.

Validate whether the validation message is fired for invalid “Password”.

Validate whether the validation message is fired for valid “Email ID” and invalid “Password”.

Validate whether the validation message is fired for invalid “Email ID” and valid “Password”.

Validate whether the validation message is fired for valid “Email ID” and empty “Password” submission.

Validate whether the validation message is fired for valid “Email ID” and another login’s valid “Password”.

Validate whether the validation message is fired for invalid “Email ID” and another login’s valid “Password”.

Validate whether the validation message is fired for invalid “Email ID” and valid “Password”.

Validate whether the Minimum & Maximum letters to be type in the text box needs to be verified.

Validate whether the page navigates to valid (Home) page after logged in.

Validate whether the application navigates to (Home) page after entering the login URL.

Validate whether the application navigates to (Home) page for browser back.

Validate whether the application password should be greater than minimum limit.

Validate whether the validation message is fired for “Email ID”, invalid symbols other than ‘@ and .’ are entered in text box.

Still writing these kinds of test case scenarios and they are not yet completed. There is no end for testing. Exhaustive testing is not at all possible.

One major thing is there which always affects the entire testing team, it’s “Time for Testing".

Have a Happy Testing Day.