Interested to Buy Any Domain ? << Click Here >> for more details...
We can check many things in one test case, then Is it
necessary to write separate test case for checking each
functionality?
Example : For Login Window -->
Test Case is--->
1) Enter valid user id & password -->
For this expected result --> 1) User should login.
My question --> while executing above valid test case,
we can expect more than one result such as
"Visibility of password should be as ****"
So Should I have to write separate test case
for "Visibility of Password" OR Not?
Please guide me properly.
- 5 Answers
- 8283 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / revati
Here you are doing only functionality testing.
That is you are checking only actual result with the
expected result.
So your test case would be when you enter valid user id and
pwd, the expected result is the user should able to login.
You do not check visibility under functional testing. In
that case you can go for UI testing.
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / sreedhar
this functionality testing,not a gui test no need to write
seperate test case.
| Is This Answer Correct ? | 0 Yes | 0 No |
what is a Bug, Defect, Error & Failure ?
what is data base testing, explain with example
Smoke testing done by whom
What is OSS and BSS?
will rapid test script wizard works in web testing?
difference between v-model and refinement form of v-model?
combo box is object or picture?
what is Regresstion testing? when it will be needed?
About Testing
after completeing testing ,what would u deliver to the client?
What are all the things should be covered in the Unit Test cases ?
1] Test Management Tool ? 2] What is tracebility Matrix? 3] What is RTM ? 4] What Is Functional testing 5] What is Regration Testing and Sanity Testing 6] Diff in Sanity and Functional Tetsing 7] Integration Tetsing 8] Diff in Primary Key and Unique Key -Should pass primary Key as null 9] What is composit Key 10] Defect Management tool in detail 11] What is Seviarity and Priority 12] Composite Key
Automation Testing 
