 |
 |
If cosmetic bugs are very low priority should we leave them and get focused on high priority tests or try to find them asap as they generates the first impact on customers?
Thats a stupid question but most of testers spend lot of time trying to find cosmetic bugs when they should try to find real bugs (I mean with Functional Impact)
by Sergio
ContinuarEven when Black box testing techniques are cheaper and easier to perform than White-Box; white-box should be a priority while we are trying to roll out. We all know about time pressure, about testers availability and testers skills but this technique can save us from big headaches:
* It’s great to validate the documentation, in some cases to create it. I’ve been dealing with some companies that prefer developing than documenting. If you check the structure of the application you ...
It’s very common to find people thinking that executing test cases is Testing but that only represents 40% of testing. Why we focus in only one task? Is it a cultura thing? Why dont we watch beyond the horizon?
Testing applies to every known stage of Development Software Process. Each stage, document, software, plan is testeable and must be tested before we perform system tests.
Besides, getting testers involved in early stages give us many benefits like saving time, identify ...
There are two major industry trends adding to the pressure. The first is accelerated release cycles. Second, while releases are more frequent and cycles shorter, the cost of failure has increased dramatically. Just a few years ago, when client server products were at the cutting edge, releases were, perhaps, annual and the expected number of users was known well in advance, because all the users were employees.
An organisation could mitigate a system failure with a manual backup. But as ...
 |
 |
 |
 |