Hot answers tagged

4

Deciding to release with severe bug (and escalate next release with a fix) or postpone release is business decision. QA cannot "assure" quality. QA can "assist" business side with information about quality and process. Business decides what is best allocation of resources: more development, or more testing, or more management and control. In situation like ...


4

This is a simple, if uncomfortable, situation to be in. Unfortunately, it does happen from time to time and you need to be ready for it. The fact that the defect has been found close to the deadline is, in the short term, irrelevant. Your team has found a high severity defect, so you report it. Given the short timescales, you ensure that everyone who ...


3

I find MITM proxies and Mocks/Stubbing to be the most advanced pieces of Technology in Automated Checking. By using these, it makes it far easier to: Create repeatable, consistent checks Decrease overall execution speed Segregate the application into logical pieces Record executed manual tests But for the real answer, QA's knowledge and senses is the ...


2

The most recent developments that I have observed are: Running tests in the cloud. Companies like Sauce Labs and Browserstack are leaders here. There are many advantages to this, from the number of devices being tested to the number of parallels servers that can be used. Writing UI tests using UI tools. Products such as Ghostinspector, heliumhq and ...


1

There is no magical answer for this. Your options include: Hide the bug and hope that the customer does not find it before you can deliver a fix. Delay the delivery until the bug is fixed. Talk to the customer about the bug and let them decide how they want to proceed. The choice depends on your circumstances, and no one here knows those as well as you ...



Only top voted, non community-wiki answers of a minimum length are eligible