Question: You have tested the application and it is released. The user asks for some changes in the project and gives one week time to complete it. Out of the one week, 6 days is taken by the developer to make the changes. So you have only one day to test it. What will you do in the case in case of manual testing?
Answer: In this situation I will prefer to consult the client and request him to extend the date of release for another 1 week, for thorough testing and fix the defects that are found, so that the quality product can be released.
Because it took 6 days to complete the coding part. Only 1 day for testing is remaining. Why are we testing? To find the hidden defects. So if you start testing the major functionalities in that single day left, found any defects. Than what is the situation? We cannot release the product, because there are defects in the major functionalities. So extending the date is the best possible way in this situation. Releasing a quality product is also as important as releasing the product on time. Client will be happy if there are no serious issues with the product, though you have took extra 1 week to release the product
Question: How do you implement a new testing process in a company which must replace existing process?
Answer: A lot depends on the size of the organization and the risks involved. For large organizations with high-risk (in terms of lives or property) projects, serious management buy-in is required and a formalized QA process is necessary.
Where the risk is lower, management and organizational buy-in and QA implementation may be a slower, step-at-a-time process. QA processes should be balanced with productivity so as to keep bureaucracy from getting out of hand.
For small groups or projects, a more ad-hoc process may be appropriate, depending on the type of customers and projects. A lot will depend on team leads or managers, feedback to developers, and ensuring adequate communications among customers, managers, developers, and testers. The most value for effort will often be in (a) requirements management processes, with a goal of clear, complete, testable requirement specifications embodied in requirements or design documentation, or in ‘agile’-type environments extensive continuous coordination with end-users, (b) design inspections and code inspections, and (c) post-mortems/retrospectives.
Question: What is difference between positive and Negative testing? Which one do you prefer as tester and why?
Answer:
Positive testing — In Positive testing, we write test case according to the specifications i.e. to pass the requirement given in the specification
Negative testing — In Negative testing we write test case opposite to the specs i.e. to fail the requirement given in the specification.
e.g. - If spec says a text box should accept 12 characters then for Positive test case we will say it should accept 12 characters and if we write test case saying enter 13 characters then it’s a negative test.
Question: Why we use WinRunner mostly why don’t we use Load Runner to test applications?
Answer: By Using Load Runner We can do only performance, stress and load testing. By using win runner we can do functional, GUI, Bitmap, Data base and Data driven testing.
Load runner is costly when we compare with WinRunner.
Read more…
What people said