Interested to Buy Any Domain ? << Click Here >> for more details...
For each bug I have to take a screen shot or For those only
which are difficult to explained?
- 4 Answers
- 5821 Views
- I also Faced
- E-Mail Answers
Answer Posted / hash
I would recommend take screen shoots it save your and
developers long communications, second you have proof for
future reference in case some defects are funny and they
keep coming back so developers will concentrate that area
and most important if you work on Agile you usually get good
feed back from Development team which is good for your profile.
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
Hi friends Does anyone have screen shot of POWERMHS and please can anyone post anything which will be helpful to understand POWERMHS. thanks.
how to explain banking domain project in testing?
what is the architecture of your current project?
can anybody send the project you have tested with the clear descriptions,and recent bugs u found in that
What is the difference between functional testing and integration testing?
Difference between Stakeholder and Relevant Stakeholder?
how to clarify functional requirements and non functional requirements in a srs?
Usually customers won’t give all the requirements. How will you manage & collect all the necessary information?
How will u decide test data to see that evey feature is thoroughly tested
name poneno dept sun 9894433467 computer This is the xls sheet a programs written to transfer this data into database write test cases and test scenario?
What is Traditional testing & Object Oriented testing?
What is common interface?
Write UI Test case, Integration Test case, Functional Test case & Performance Test case for the File Menu for MS-Word?
what does 80hz refresh rate indicates?
How many bugs occured will be considerd appropriate over 1000 steps when inspecting software? Describle an approriate Bug value.
