Welcome to Testing land
This is an example post, originally published as part of Blogging University. Enroll in one of our ten programs, and start your blog right. You’re going to publish a post today. Don’t worry about how your blog looks. Don’t worry if you haven’t given it a name yet, or you’re feeling overwhelmed. Just click the… Read more
What is the difference in Use case and Test case?
As the name suggests Use case is how the user will use the product. There are defined steps that more so are focused towards user experience. So Use cases are written and executed to understand if the requirement is fulfilled or not. Use cases are for development team to understand what to develop.
Test case are the defined steps that are specific to testing a function in the system. They are the steps given to testers to test and see if the function that is developed is as per the requirement document. So in a way the use case act as an input for the test case.
Which phase of SDLC does the testers begin to write test case?
In SDLC after the completion of FRS (Functional Requirement Specification) document, the test lead prepares the Use case document and Test plan document. It is then the testers start writing the test cases.
What is the difference between functional document and business document?
Bussiness document is the outcome of defining requirements stage of SDLC. In this document business solution to the proposed business problem is documented in the form of use cases and business process diagrams. These requirements specify “what” the system must do in order to fulfill the requirements of the business. The business rationale explains “why” the business requirement is necessary. This is often important later if analysts or developers have questions regarding the purpose or validity of the requirement. The rationale can be used to support the need for the business requirement or clarify ambiguous language by providing a context for the requirement.
In contrast, the FSD defines “how” the system will accomplish the requirements by outlining the functionality and features that will be supported by the system. Ideally, the functionality of the system will be described in logical terms so that the FSD is technology and platform independent. Many FSDs include screen mockups or wireframes for communicating the layout and design of the system screens. Many FSDs include screen mockups or wireframes for communicating the layout and design of the system screens.