TE Quiz

Testability in SDLC

TE Quiz

What is the main goal of a testability review in product and tech design?

1: What is the main goal of a testability review in product and tech design?

To check if the product looks good

To estimate project budget

To ensure the system is easy to observe and control during testing

To finalize deployment strategy

Which of these factors most directly impacts testability?

2: Which of these factors most directly impacts testability?

Code indentation

Team size

Availability of logs and metrics

UI color scheme

During a product spec review, which testability aspect should you check first?

3: During a product spec review, which testability aspect should you check first?

How test data will be created and managed

If the UI mockups are pixel perfect

What the deployment environment looks like

Who is writing documentation

A service has no clear error codes, only generic 'Something went wrong.' What is the testability issue?

4: A service has no clear error codes, only generic 'Something went wrong.' What is the testability issue?

Limited observability

Security risk

Poor scalability

Inefficient automation

Which design principle helps improve testability the most?

5: Which design principle helps improve testability the most?

Single Responsibility Principle

Copy-paste programming

Hardcoding values

Tight coupling

When reviewing a tech design, which is a red flag for testability?

6: When reviewing a tech design, which is a red flag for testability?

APIs have versioning

Multiple hidden dependencies

Logging is configurable

Clear monitoring hooks

What role does mocking & stubbing play in testability?

7: What role does mocking & stubbing play in testability?

Improves security

Helps simulate unavailable systems

Reduces production costs

Automates deployment

In integration testing, what improves testability of data flows?

8: In integration testing, what improves testability of data flows?

Hardcoded production credentials

Manual database updates

Synthetic data generators

Disabling validations

A team proposes a black-box system with no external APIs, only UI. What’s the testability challenge?

9: A team proposes a black-box system with no external APIs, only UI. What’s the testability challenge?

Limited automation and observability

High cloud cost

High latency

Complex UI design

Which of these should be systematically included in product & tech reviews from testability perspective?

10: Which of these should be systematically included in product & tech reviews from testability perspective?

Metrics, logging, test hooks

Team hierarchy charts

Brand color palette

Competitor analysis