Software QA Flashcards

1
Q

When the product is good enough to be released?

A
  • When major bugs are fixed
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

How do you determine when you have done enough testing?

A

Number of open bugs does not decrease over time (quality of product does not improve over time)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

When do you automate testing?

A
  1. when testing cannot be done manually:
    • multi-user
    • load
    • stress
    • performance
  2. When the test is expected to be launched many times
    • build acceptance (the most frequent) - done as many times as we have builds
    • regression (second most frequent) - done against builds, which passed the build acceptance test
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

When does TESTING begin?

A

Development stage - after the code is ready to be tested

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

When does QA begin?

A

Begins from day one with analysis & requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

If you found a bug what do you have to do next?

A

Report it immediately (unless instructed otherwise) upon making sure the bug is reproducible

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

If you find a bug and the developer says it is as-designed, what would you do?

A
  • First make sure the developer is right - do not take her words as 100% truth.
  • Then close the bug if she is right.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

How do you perform UI testing?

A
  • WEB application - Along the usability guidelines published on www.usability.gov
  • Windows application - Along the GUI guidelines published by Microsoft
  • iOS application - Along the guidelines published by Apple
  • Android application - Along the guidelines published by Google
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

If you log a bug and the developer says she cannot reproduce it, what should you do?

A

-Make sure it was not fixed earlier (is still reproducible on your system)
-make sure the bug was properly communicated to the developer
-Compare the environments: OS, version of the product, browser, etc.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is re-testing?

A

Re-testing is running same test again after a while

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Describe the QA Process

A

Test Planning Process

Test Development Process

Test Execution Process

Defect Management Process

Test Reporting Process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly