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
- 8063 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 |
Hi, Im B.E 2011 pasout,worked in back office till now, but now im searching for job into manual testing with fake exp of 1 year..Plz suggest me how to prepare for an intervw? how to gain real time testing knowledge? Is dere any site where i can practice testing?
what is a test analyst? what are his responsibilities?
What is difference between regression testing and re- testing?
explain v- model? why we call this model as v-model, not an u-model?
What is disaster testing and recovery testing ?
Want to learn Manual Testing in just two days? Students around Thanjavur, Trichy, Mayavaram and Kumbakonam Mail to manualtestingtraning@gmail.com. Entire Manual Testing Concept. Any doubt regarding IT Job please mail above ID
I need a Test case templetes for Yahoo Mail ID
in an online banking software,users are connecting to bankserver by login.This login module can take below inputs for user. a/c number prefix-3 digits but doesnot start with 0&1 a/c number sufix-6 digits number password-5to 10 chars alphanumerics in lowercase areacode-3 digits number but optional purpose- cheque deposit money trasfer mini statement bills pay After filling above fields,user can click submit button to connect to bank server.prepare test scenarios for online banking s/w login.
When a bug posted by QA is rejected by Dev and Dev says is not a bug. How to convince Dev that it is a valid bug?
if google wants to introduce the third button along with "search" and "iam feeling lucky",what u will propose and how will u test it?
I Have a login screen.Jus before the release you see the screen and there is a bug.Tell mde wats the bug. screen : Logen : Password : | Submit |(submit is a button)
1.what is test scenario? if possible give me some documents? 2.what's the difference between test scenario and frs?
Automation Testing 
