what are the do's and dont's of a tester?
Answer / novic
Do's:
1.Understand the thorough knowledge of application
2. Think different scenarios per funtion
3. Make a attitude of breaking the application
4. Have good rappo with developers team
5. do write test cases lots for functions
6. follow the timelines, test plan regularly
7. make a habit of documentation of each and every work
your doing
8. send the daily status, to the reporting team and check
it out in cm tool.
9. solve your system issues on your own which leads you
more confident.
10. reduce your rework in all phases.
11. Make effective description so that developers will
understand the bug easily
Don'ts:
1.Don't overtake developers
2.Don't hide bugs just to make your bug count high
3.Don't be tired of testing, do as much as you can
4.Don't think what you have done is enough
5.Don't be harsh to explain your views to others in tough
situation
please comment me, if i am wrong?
| Is This Answer Correct ? | 4 Yes | 1 No |
what are the different testing methodologies and testing techniques? Am asked in interview that what is the defect age? I replied that the time gap between the defect reporting and defect resolving. then the interviewer asked me if at all the defect is not resolved then what is the defect age of that particular defect? can anybody answer this?
you are testing with daily builds,you installed the latest build today and what will you do if the application shortcut is not launching?
Please explain software release process in detail.
What are the differences between V-Model and Agile Model?
What are the properties of a good requirement?
Am putting E-commerce project in my resume can any one please tell me about E-commerce application explaination..
what is Adittrail in test factors
explain waterfall module.
How to make sure test cases that you have written are good enough?
Can u any 1 please explain the below question and answer? Given the following code, which statement is true about the minimum number of test cases required for full statement and branch coverage? Read p Read q IF p q > 100 THEN Print "Large" ENDIF IF p > 50 THEN Print "p Large" ENDIF a) 1 test for statement coverage, 3 for branch coverage b) 1 test for statement coverage, 2 for branch coverage c) 1 test for statement coverage, 1 for branch coverage d) 2 tests for statement coverage, 2 for branch coverage
There is an application which is to be used in different countries . My question is what are the most common checklst that are to be followed for testing it.
what are the common errors while doing integration,system,functional,regression,user acceptance testing? can anybody please let me know the answers it is too urgent???