Can You Answer These? A List of Tricky Questions for Pro Testers!


2 m read


Tips & Tricks

Double-checking is something any tester is destined to do 24/7. How about making sure your theoretical background is not all rusty? We came up with a little quiz over few past days designed for testers. Will you be able of answering all questions without a peek in the answers? Let’s find that one out, shall we?

  • What is the right flow of resolving found issues?
    • 1) record, meaning log everything troublesome that took place while you were running a test;
      2) report: properly report the issues to people responsible for them;
      3) control: issue management process is to be defined.
  • How does Retesting differ from Data Driven testing?
    • DDT is the process when different test data is being used for app testing, meaning various sets of values are used when retesting is the process when testers acre double-checking and validating defects that are claimed as fixed by development side.
  • A latent effect? What can one possibly mean by that?
    • It’s when you know there’s a defect in the system, you know its location and the defect is not causing any crushes or failures. It’s just there until a certain set of conditions (which may never even come true) is met.
  • What’s N+1 testing?
    • A nice variation of regression testing. There are multiple cycles where tests ape performed. And the defects that have been resolved in the N cycle are being retested in the N+1 cycle.
  • What’s a DFD?
    • DFD stands for Data Flow Diagram. Basically if the process of the data flow through any information system is expressed in a diagram it will be a DFD.
  • Is Fuzz testing quite?
    • Well, one may say so if he believes that adding various random data inside the system with one single goal of crushing it is quite.
  • When’s the perfect time to prepare the RTM? And what’s RTM in the first place?
    • RTM stands for Requirement Traceability Matrix and as we all know requirements are and ought to be traceable straight from the review activities.
  • Explain fault masking!
    • Defects working together when one is hiding the other.
  • What do we call mutation testing?
    • What will happen if code is changed on purpose? After placing new bugs use old test data for retesting and determine how useful your test cases and sets of data are.

And you are done with our little quiz! Peace of cake you said? Well, that means you are an actual pro, but only constant practice makes perfect. Let us know if you have enjoyed this quiz and whether you want more from where this came from. Remember: you can’t afford getting rusty when working in quality control and quality assurance.

Realizing the importance of providing service on agreed terms, we consider all possible risks and provide efficient solutions for all possible risks and provide efficient solutions.


We use cookies to ensure your best experience. By continuing to browse this site, you accept the use of cookies and "third-party" cookies. For more information or to refuse consent to some cookies, please see our Privacy Policy and Cookie Policy