Across
- 2. A technique ensuring that software meets industry regulations.
- 4. The state of being too confident in one’s knowledge, leading to errors.
- 6. Detailed documentation describing a software defect.
- 7. The separation between developers and testers to avoid conflicts.
- 9. The psychological factor where a person’s cognitive resources are overwhelmed.
- 10. The act of locating and documenting issues in software.
- 11. The ability to understand another person's emotions and perspective.
- 12. The psychological factor that affects perception in testing.
- 14. Objectivity in assessing software quality.
- 16. The process of continuously improving communication skills.
- 20. The type of testing performed by a team separate from development to ensure impartiality.
- 21. The collaborative process of developers and testers working together to improve quality.
Down
- 1. The process of evaluating and verifying that software does what it is supposed to do.
- 3. The bias where people favor information that confirms their preexisting beliefs.
- 5. The practice of using automated scripts to execute tests.
- 8. The act of running tests without predefined scripts to explore the software.
- 13. The end result of effective testing and communication, ensuring customer satisfaction.
- 15. Another term for mistakes in software.
- 17. The role responsible for identifying defects and ensuring software quality.
- 18. Ensures a high degree of independence in testing, often outsourced.
- 19. The role responsible for writing and maintaining application code.
