Exit this survey Test Documentation 1 Question Title * 1. What is test case? Steps of bug report to be executed for verification of fixed bug Making sure one or more requirements are properly implemented Another way to refer to a test scenario Use Case, steps of how user will test the application Set of conditions and/or variables under which a tester will determine if a requirement upon an application is satisfied Format used by business analyst for specifying system requirements Short description of a bug report Step-by-step instruction on how software feature should be tested Other (please specify) Question Title * 2. What is included into the Test Case at the time of planning? Expected result Report a bug after discussing it with QA Manager or QA Lead Pass/fail indication Steps to reproduce Short description An instruction on how to get from the application base state to a verifiable application output or expected result Test Case ID Actual result An instruction on how to resolve the problem Other (please specify) Question Title * 3. What are the most common documents written by testers? Test Plans Steps to reproduce Bug Reports Traceability Matrices End-to-End Tests Test cases Use Cases Requirements Test Matrices Other (please specify) Question Title * 4. Which documents would you refer to when creating Test Cases? Will develop the product first and then write the requirements Will rely primarily on my intuition Use Cases Functional Specifications Meeting Notes BRD - Business Requirements Document All business and technical documentation available Emails from customers Will rely primarily on my product knowledge Test Design Third party publications (books, published by independent authors) Manuals and Help PRD - Product Requirements Document Other (please specify) Question Title * 5. Write test cases for LOGIN/PASSWORD dialog box: positive and negative Question Title * 6. What is the difference between a test case and a test plan? No difference Test plan needs to be approved by QA Manager Test cases are an integral part of the test plan Test cases are written by testers, test plan - by QA Manager Test cases are about finding bugs; test plan is about preventing them Test cases are about meeting requirements; test plan is about test strategy, schedule, resources Question Title * 7. Describe risk analysis Business Analyst's responsibility Assessing risk of not hiring enough testers for the project Actions taken to avoid things that might negatively impact the scope, quality, timeliness, or cost of a project Analysis of how customers will react on software problems Shared responsibility among everyone involved in a project Marketing meeting where new features are discussed Other (please specify) Question Title * 8. What is Test matrix? Matrix of tests Spreadsheet for organizing and presenting test data Risk analysis methodology Format for specifying system's requirements Data collection mechanism Debt collection mechanism Other (please specify) Question Title * 9. What is a test plan? Developed by business analysts to meet the requirements Collective work of QA Team on software testing risks Document that describes the objectives, scope, approach, and focus of a software testing effort. Table of content followed by multiple chapters Other (please specify) Question Title * 10. What does Test Plan include? Personnel allocation Feedback from company management Use Cases RE Appraisal Report Testing priorities and focus Test Scenarios Expected results Steps to reproduce Test Matrices Risk Analysis Other (please specify) Done