If we don't caught any bug in all build, then what we can
say -
1. Bad Coverage
2. Excellent Coding
3. Bad Testing
Answer Posted / shubhra
Hi
As per Test engineer’s opinion, there are just 0.00001%
chances when you will not find any bug in any of the builds.
In real time scenario this never happens.
However if it happens after better testing coverage and
quality then we can surely say that, the coding is excellent.
Please correct if my analysis is wrong.
Thanks.
| Is This Answer Correct ? | 3 Yes | 2 No |
Post New Answer View All Answers
what is the SOAP UI and Web services? what are the uses in testing?
What is difference between retesting and regression testing?
write an e-mail introducing yourself to the client as a QA ead is not in town.
What is basic block?
iq test
What is software process?
Case Study:-Given a standard calculator with the basic functionality of addition,substration,multiplication and division-write the test case to test this and tell how did it take to write the above test case and how ling would it take to execute them?
List out the roles of quality assurance engineer?
Explain the benefits of destructive testing.
How validation activities should be conducted?
What is the difference between compatibility testing and cross browser testing?
What is the difference in responsibilities of programmers and qa analyst?
What are the challenges you faced related to production environment bug?
'configuration related errors' in testing means what?
We have a directory structure /usr/local/jboss/server/{$app_name}/log/*.log which contains 1000 log files. A web application has been logging to the cloud.log file, the attempts of a user called test. The code logs the following way: log.debug(username); where the username equals “test”. What command line application and or combinations of applications will you call in order to create a file named user_log.csv that contains the following lines, where the timestamp is sorted: timestamp,username