Implementation and Quality Assurance

Question 1

What is software quality

Answer 1

The degree to which a system, component or process meets:
- Specified requirements
- Customer or user needs expectations.

Question 2

What is software quality assurance? (SQA)

Answer 2

A planned and systematic patter of all actions to provide adequate confidence that an item or product conforms to the established technical requirements.
- set of activities to evaluate the process by which the product is being developped or manufactured.

Question 3

Verifications vs Validation:

Answer 3

Verification: Are we building the product right?
Validation: Are we building the right product?

Question 4

Static vs dynamic V&V

Answer 4

• Static: analyzing the code
• Dynamic: Executing the code.

Question 5

Advantages of static of dynamic

Answer 5

dynamic requires executable code, static does not.
Inspections discover inneficiencies and style issues.

Question 6

What are inspections not a replacement for?

Answer 6

Inspections are not a replacement for tests
- People cannot catch eveything
- We still need tests to ensure the code function correctly.

Question 7

Roles in QA

Answer 7

Author: responsible for correcting problems that are identified during the review.
Reviewer: analyzes and detect problems in the artifacts
An engineer with expertise in the context that the artifact operates within

Question 8

QT code review process:

Answer 8

1) patch uploaded
2) sanity check by early warning system.
3) code examination by reviewers
4) Integration testing by CI system.

Question 9

What is testing?

Answer 9

A formal process carried out by a specialized testing team in which a software unit, several integrated software units. or an entire software system are examined by running the programs on a computer.

Question 10

What is the “ugly truth about testing”

Answer 10

• Large input and state spaces (impossible to test everything)
• Lack of continuity: Small differences in operating conditions can dramatically impact software behavior.

Question 11

What are blackbox and whitebox tests:

Answer 11

Blackbox:
-tests that are written without considering how the code is written
-Treats the system like an opaque box that accepts inputs and checks outputs.

Whitebox testing:
-Tests that are written with an understanding of the structure of the code
-tests the inner workings of the system itself.

Question 12

What are the testing stages

Answer 12

Development testing
release testing
user testing

Question 13

What is development testing:

Answer 13

-tests that are typically written by system designers and programmers

Question 14

What is release testing

Answer 14

• separate QA team produces tests to check the system before it is released.

Question 15

What is user testing:

Answer 15

tests run by the user to make sure they are satisfied witht he testing.

Question 16

What are the key phases of unit testing:

Answer 16

-Setup part: Prepares the system for executing the test case
-Call part: Call the method under test
-Assertion part: Check that the system state is in its expected form
-Teardown part: Reset the system to its pre-setup state

Question 17

What is equivalence partitioning

Answer 17

Inputs and outputs can be thought of as members of sets with common characteristics
Rule of thumb
Select test cases on the edge of the partitions
Select a test case near the middle as well

Question 18

What is an equivalence class:

Answer 18

You should divide the possible inputs into groups which you believe will be treated similarly by all algorithms.
Such groups are called equivalence classes.

Prevents brute force testing on ALL cases

Question 19

Types of component interfaces

Answer 19

Parameter:
Passing parameters through method calls
Shared memory:
Accessing a shared program element
Procedural:
Interfaces in the typical (OO) sense
Message passing:
A message is sent to request some service (e.g., client-server applications)

Question 20

Types of interface errors

Answer 20

Misuse:
Caller makes an error in the use of an interface
Misunderstanding:
Caller makes an invalid assumption about the use of an interface
Timing:
Some interfaces are time-sensitive
Even if a caller uses an interface correctly, it may be too early/late

Question 21

What is system testing

Answer 21

Target: the combination of components that make up a subsystem or the entire system
Focuses on testing the interactions between components

Question 22

What is release testing:

Answer 22

Similar to system testing, release testing is performed on the entire system and is based on use cases