Testing

Edit Answers
12345678910111213141516171819202122
Across
  1. 7. Testing and test design without using knowledge of the code.
  2. 8. Using knowledge of the code and how it has been put togethe.
  3. 10. How well-defined or easy to use a product is.
  4. 13. defines the value of a product, although this can be subjective depending on the stakeholders and the product.
  5. 14. A test technique used to show different versions of the same feature to end-users to determine whether one yields better results.
  6. 16. The measure of how well a system handles increases in work demand based on performance and cost.
  7. 18. Every time someone commits a change, an application is built and a comprehensive set of automated tests are run against it. The goal is to have the application in a working state at all times.
  8. 20. A small number of tests run to see if the system will start to break after a build.
  9. 21. A test written by domain experts or customers to determine if software meets specifications.
  10. 22. Testing and test design that focuses on the individual features of an application.
Down
  1. 1. Testing like Indiana Jones
  2. 2. Commonly confused with system testing. Testing complete business flows across one or more systems.
  3. 3. Are you building the software properly and implementing it correctly according to specifications.
  4. 4. Determines whether a product is usable by people with disabilities.
  5. 5. Abbrv for a method of prioritising tests based on business, technical and other prioritites
  6. 6. when a newly introduced change causes issues with working functionality in a system.
  7. 9. Abbrv - A style of software development that focuses on writing the minimum amount of code to make it pass pre-defined tests
  8. 11. Uses mathematical and visual representations of what a system might do in order to determine if the test is passing or failing.
  9. 12. This assesses whether a user or the maximum number of users could overload a system’s resources.
  10. 15. Are you building the right software to solve the customer’s problem or meet their expectations.
  11. 17. A single module or function
  12. 19. This combines your test strategy, your logistics, and your project risk management to document how you will do things.