All featured quizzes

Testing - Basics

Test cases, verification vs validation, sanity testing, stress testing, and boundary value analysis.

Sample Questions

A preview of what's in this quiz. Answer them interactively for instant scoring and full explanations.

What is Black-Box Testing?

1. What is Black-Box Testing?

  • A.Testing the functionality of software without knowing or accessing its internal code structure.
  • B.Testing only the dark mode theme layout rendering of the application.
  • C.Analyzing the compiler warnings and binary file sizes statically.
  • D.Testing the database queries by writing raw SQL commands directly.
What is a Test Suite?

2. What is a Test Suite?

  • A.A collection of related test cases grouped together for execution purposes.
  • B.A software application used by developers to write code classes.
  • C.A server node that hosts the testing databases and config secrets.
  • D.A set of programming variables declared in unit test headers.
What is White-Box Testing?

3. What is White-Box Testing?

  • A.Testing that analyzes and verifies the internal structure, logic, and code paths of the application.
  • B.Testing the application's user interface using black-and-white browser screens.
  • C.Evaluating the software purely based on external functional requirements.
  • D.Testing the application on hardware servers that are color-coded white.
What is the difference between verification and validation in software testing?

4. What is the difference between verification and validation in software testing?

  • A.Verification checks if the product conforms to specifications; Validation checks if it meets user needs.
  • B.Validation checks if the product conforms to specifications; Verification checks if it meets user needs.
  • C.Verification is done by compilers; Validation is done manually by end-users.
  • D.Validation checks code formatting; Verification checks database connection speed.
What is the primary purpose of software testing?

5. What is the primary purpose of software testing?

  • A.To identify defects and verify that the software meets specified requirements.
  • B.To write the source code for the application's user interface.
  • C.To design the database tables and set up index keys.
  • D.To compile the application into executable machine binary files.
What is a Unit Test?

6. What is a Unit Test?

  • A.A test that verifies the correctness of a small, isolated piece of code, such as a single function.
  • B.A test that evaluates the interaction between multiple sub-systems and databases.
  • C.A test that measures the response time of the application under high user traffic.
  • D.A test executed by end-users in a production-like environment before release.
What is a Test Case?

7. What is a Test Case?

  • A.A set of conditions, inputs, and expected outcomes designed to verify a specific behavior.
  • B.A database table where system bug logs are stored for debugging.
  • C.A tool used to compile source code files into binary packages.
  • D.A programming structure used to handle run-time error exceptions.
What is Regression Testing?

8. What is Regression Testing?

  • A.Re-running existing tests to verify that new code modifications have not introduced bugs into working features.
  • B.Testing the application's maximum database query speeds under concurrent load.
  • C.Running security scanning tools to identify licensing issues in libraries.
  • D.Testing the application on older legacy operating system versions.
What is Manual Testing?

9. What is Manual Testing?

  • A.Executing test cases manually by a human interacting with the software interface.
  • B.Running command-line scripts to compile source files to executables.
  • C.Writing automated test code that executes in the CI/CD pipeline.
  • D.Entering data manually into production databases using administrative tools.
What is Integration Testing?

10. What is Integration Testing?

  • A.Testing the interface and interactions between two or more combined software components.
  • B.Testing a single function in complete isolation from the rest of the codebase.
  • C.Validating the spelling and grammar of text labels on the user interface.
  • D.Running security penetration scripts against the production environment.
What is User Acceptance Testing (UAT)?

11. What is User Acceptance Testing (UAT)?

  • A.The final testing phase where business users verify that the software is ready for production deployment.
  • B.Testing the loading times of application pages under high network latency.
  • C.Running automated unit tests to verify individual function code branches.
  • D.Checking the database configuration parameters for security compliance.
What is Automated Testing?

12. What is Automated Testing?

  • A.Using software tools and code scripts to execute tests and verify results automatically.
  • B.Deploying the application to cloud servers automatically when builds pass.
  • C.Letting the compiler fix code syntax errors and formatting style issues.
  • D.Letting artificial intelligence write the entire application source code.
What is End-to-End (E2E) Testing?

13. What is End-to-End (E2E) Testing?

  • A.Testing the entire application flow from start to finish, mimicking real user behavior.
  • B.Testing only the final compile stage of the application's build script.
  • C.Running unit tests repeatedly in a continuous loop until they fail.
  • D.Checking the network cables and database connections at both ends of a cluster.
What is Sanity Testing?

14. What is Sanity Testing?

  • A.A quick, focused check to verify that specific bug fixes work and the system is stable.
  • B.Testing the database replication delay across remote server clusters.
  • C.A full, comprehensive manual test of every feature inside the application.
  • D.Running automated tests on production servers using real user data.
What is Alpha Testing?

15. What is Alpha Testing?

  • A.Internal testing performed by the development team and QA staff inside the organization.
  • B.External testing performed by real users in their own environments.
  • C.Testing that verifies the application compiles on Linux runners.
  • D.Performance testing to measure how many users the server can support.
What is Load Testing in performance evaluation?

16. What is Load Testing in performance evaluation?

  • A.Testing the software's performance under expected normal and peak concurrent user counts.
  • B.Measuring the physical weight of server racks inside a data center.
  • C.Testing the loading times of images under slow network environments.
  • D.Uploading large database files into cloud storage S3 buckets.
What is a Test Plan?

17. What is a Test Plan?

  • A.A document outlining the testing scope, strategy, schedule, and resources for a project.
  • B.A code file containing class variables and test assertion methods.
  • C.A list of database indexes that need to be created for optimization.
  • D.A dashboard that shows the real-time execution logs of running servers.
What is a Bug or Defect in software development?

18. What is a Bug or Defect in software development?

  • A.An error in the software that causes it to behave incorrectly or fail requirements.
  • B.A hardware device used to connect servers to network routers.
  • C.A library dependency that has been deprecated in modern versions.
  • D.A temporary folder used by the operating system to store caches.
What is the difference between Functional and Non-Functional testing?

19. What is the difference between Functional and Non-Functional testing?

  • A.Functional checks what the application does; Non-functional checks how it performs (speed, load, security).
  • B.Non-functional checks what the application does; Functional checks how it performs.
  • C.Functional testing is automated; Non-functional testing is always manual.
  • D.Functional testing is for APIs; Non-functional testing is strictly for HTML layouts.
What is Stress Testing in performance evaluation?

20. What is Stress Testing in performance evaluation?

  • A.Testing the software behavior at or beyond the limits of its capacity to find breaking points.
  • B.Evaluating the project developers' mental strain during tight deadline sprints.
  • C.A test that verifies encryption configurations under slow server speeds.
  • D.Running compilation scripts repeatedly until the disk storage is exhausted.

Looking for a different topic? Browse all subjects