Quality is delighting customers
Test cases are written on the basis of functional documents. at the time of write test case we consider both positive & negative test cases.'Is Negative Testcases must be an Invalid Testcase?' No, when we execute all test cases If negative test cases are fail then they are fail test cases
Negative test cases are the part of the particular requirement, as tester have to cover all the area of the test cases so its include the negative testing and this is the part of requirement.
We cant say that this a invalid testcases.
Test cases are written on the basis of requirement. Positive testcases , negative test cases m Invalid testcases .
Example :- We need to write test cases for a query which pulled item whose pricing is > 65 rs per bundle and sale b/w 1 April 30 April to data from databases
Positive test cases :- Find the Name of item which sale on 13 april and and per bundle cost is 65
Negative test case :- Find name of item which sale on 31 March and per bundle cost is 65 rs .
Negative test case :- Find name of item which sale on 1 May and per bundle cost is 65 rs .
Invalid test cases : -We trying to find item from this query whose pricing 65 rs per bundle and sale on 14 March.out of scope we checking
so we can say invalid test cases those which are out of scope of functional requirement.
There is no negative test case, there should be negative testing which consists invalid input, which is a part of functional testing.
Negative testing is done to check how the application behaves in that case...
and we can have to cover Valid test case and invalid test case in functional testing
lets assume a first name field which is accepting 30 chars
we will partition this in three different partition
1- invalid partition -- 0 -- which is inavlid test case which contains invalid input
2. Valid partition - 1 to 30 characters -- which is valid test case which contains valid input
3. Invalid partition -- more than 30 -- which is invalid test case which contains inavlid input
4. Valid Partition -- 1 to 30 with alphanumeric -- which is invalid test case which contains invalid input
Thanks for you reply,
I would like to mention my view on the above.
Consider Example: Login Page>> Text box [User Name 6-12 characters] >> enter [Submit]
Valid Test case: Enter valid 'User Name' [Either name/ Email ID], press Submit.
Positive Testcase: Enter valid 'User Name' [Jegan1], press Submit.
Both case is similar
Invalid Testcase: Enter invalid data in the 'User Name' field [enter 5 character]and press 'Submit'.
Negative Testcase: Enter invalid data in the 'User Name' field [Symbols] and press 'Submit'.
Please let me know If it is incorrect.
Jegan Raj Kumar S
1. To know negative or positive test cases first you need to know the scenarios.
2. To know negative scenarios you need to know the validations on various fields.
3. Depending on validations, choose a test design techniques to decide on the data that you are going to use while testing.
4. Form combinations on this data.
5. Rank the combinations.
6. Select the combinations for testing.
7. Write the test cases.
Example: Login Screen.
1. It has two fields: ID & Password.
2. ID has to be valid employee ID (numeric) and password has to be matched with a stored one.
3. User can click on Cancel if wants to discontinue. Upon clicking on Cancel the application closes. (In case web application either browser closes or the tab closes.)
4. Upon clicking on Forgot Password link another form gets displayed.
5. Upon successful login, user gains the access of system.
6. Upon 3 consecutive unsuccessful attempts the User gets blocked, user gets appropriate message and upon clicking on that message the application closes.
7. After entering ID & Password, Submit button gets enabled.
Now, what are Positive and Negative scenarios?
1. ID & Password matches and user clicks on SUBMIT button.
2. Clicking on Cancel Button.
3. Clicking on Forgot Password.
1. ID is wrong, Password is correct.
2. ID is correct, Password is wrong.
3. ID is blank, Password is correct. (In this case SUBMIT Button should not be enabled)
4. ID is correct, Password is blank. (In this case SUBMIT Button should not be enabled)
5. ID & Password both are blank. (In this case SUBMIT Button should not be enabled)
6. ID & Password both are wrong.
Some examples of negative test cases are:
1) Say you have to enter mobile no to get the bill detail in report - so enter a mobile no that does not exist eg a negative no, or a very large no etc
2) If there is a score field(where toy have to provide score/points) enter character and check. A pop should display saying that only numeric characters are allowed
3) For the above scenario only, if the score is to be given out of 100, then try to enter points above 100,a pop up should come saying "mAx limit is 100" or any other similar comments
4) similar kind of test cases - where in place of character values enter numeric values or vice versa and try to run the report. A popup with an appropriate message should come
There is nothing like invalid test cases as testing is never ending risk based activity and we cant ensure 100% coverage.
While testing we need to consider positive scenarios and negative scenarios.
Positive scenario are mostly stated requirements however negative may be stated or not stated requirements.
If we consider login to apllication scenario then positive scenario will be you should be able to login to application with valid username and password. Negative scenario will be consists of all the test cases which will not allow you to login.
Again for each of the field you can do negative testing by invalid inputs.