1 / 14

Required Document Collection For Test Case Writing

A test case has to be written by software tester right from the beginning stage of software development life cycle itself and is desirable at the time of software requirements phase. <br>

janbasktraining
Download Presentation

Required Document Collection For Test Case Writing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Required Document Collection For Test Case Writing www.janbasktraining.com

  2. “ Software Testing is a process of executing a program or application with the intent of finding the software bugs. It can also be stated as the process of validating and verifying that a software program or application or product: Meets the business and technical requirements that guided it's design and development.” www.janbasktraining.com

  3. A test case has to be written by software tester right from the beginning stage of software development life cycle itself and is desirable at the time of software requirements phase. • It is the responsibility of a Test Manager or a QA Manager to collect and prepare maximum documents as listed below. www.janbasktraining.com

  4. Document Collection • It is a document that outlines the business process, user environment and user profiles to name among a few. • Other key essentials that have to be included within the User Requirements Document are as given below. • User interaction with other systems • Functional Requirements • User Requirements Document www.janbasktraining.com

  5. Performance Requirements • Non-functional Requirements • Licensing and Installation Requirements • Usability and Concurrent Requirement • Security Requirements • Replacement of Existing Systems www.janbasktraining.com

  6. Business use case document explain the details regarding the use case scenario of the functional requirements right from a business point of view. • Business Use Case Document covers : • System • Goals • Business Use Case Document www.janbasktraining.com

  7. Pre-conditions • Post-conditions • Basic Flow • Alternate Flow • Options • Exceptions related to each of the business flow in a system under the requirements www.janbasktraining.com

  8. Functional Requirements Document • As the name suggests, this document provide details about the functional requirements for each feature corresponding to the system under requirements. • This document is considered as a common repository for software developers, software testers and the project stakeholders that even include the customers for which the requirements have been already committed. • Therefore it is considered as the most important documents that are required for test case writing. www.janbasktraining.com

  9. This is a document that describes in detail about the project and its objectives. Other details that is available within a Software Project Plan would be. • Software Project Plan (Optional) • Priorities • Activities • Milestones • Strategy • Risk Analysis www.janbasktraining.com

  10. Progress Monitoring • Organization Structure • Assumptions • Dependencies • Constraints • Risk Analysis • Training Requirements • Client Responsibilities • Project Schedule www.janbasktraining.com

  11. This document provides details about the quality management system as well as documentation standards. • Other details available within this document include: • Change Control Mechanism • Critical Modules and Functionalities • QA/Test Plan www.janbasktraining.com

  12. Testing Plans • Acceptance Criteria • Defect Tracking • Configuration Management System www.janbasktraining.com

  13. Testing plan document however is more about the procedure to identify features that have to be tested and features that does not have to be tested. • It is also comprised of information regarding the resource requirements, test case writing, test coverage, testing schedule, bug reporting, test deliverables, bug reporting, testing team allocations and their interface, pre-requisite for test execution, test metrics and tracking mechanism etc. www.janbasktraining.com

  14. THANK YOU Address: 2011 Crystal Drive, Suite – 400 Arlington, VA – 22202 Contact @ +1 908 652 6151 Mail us: info@janbasktraining.com Website: https://www.janbasktraining.com For Business Analyst:https://www.janbasktraining.com/online-qa-training

More Related