16 What is the difference between a use case and a test case? Use Cases and Test Cases are two important terms in the context of Software Testing. A use case tells how a System will behave or perform a certain task provided the given conditions and a test case contains the actual test data, set of instructions to the system and the expected result of the interaction with the system Following are the important difference between Use Case and Test Case. Sr. No. Key Use Case Test Case 1 Objective The objective of the Use case is to ascertain a certain output after the set of operations. The objective of the test case is to ensure that system is working fine for each given instruction and yields the required result. 2 Definition Use case is a representation of actions that describes the behaviour of the system to do a particular task. A test case contains the test data, a set of instructions to follow and a result(s) of following the ins...
Posts
15 How do you go about writing test cases for a given requirement? A Test Case is a set of actions executed to verify a particular feature or functionality of your software application. A Test Case contains test steps, test data, precondition, and postcondition developed for a specific test scenario to verify any requirement. Industry connect
13 Why do you need screenshots and logs to be attached to a defect/bug? When a bug cannot be displayed on a snapshot or video file, individuals use logs during software testing. It usually occurs when there has been an emergency shutdown. In this situation, all of the steps must be recorded in the logs. These attachments contain all of the information needed to complete all of the steps. Different attachments for different situations: If there is a snapshot/video file, developers may overlook the description and instructions. This is why it’s crucial to know when and how to use each attachment based on the situation. The most common type of attachment when we describe visual problems (interface, layout) is a screenshot. The files you attach must be entirely informational. A screenshot should be taken if there is a fault with the cursor. It often appears that a screenshot is unnecessary because everything is obvious. However, past experience has shown that discovered bugs a...
12 How do you log bugs/defects? Defects logging, is a process of finding defects in the application under test or product by testing and recording feedback from customers and making new versions of the product that fix the defects or client feedback. Defect tracking is an important process in software engineering as Complex and business-critical systems have hundreds of defects. One of the challenging factors is Managing, evaluating and prioritizing these defects. The number of def...
11 What would you do during the Test cases development phase in STLC? In this phase, the QA team writes the test case with a stepwise approach. The Test Case is then signed off by a Business Analyst after reviewing or rework on test cases in case modifications are required. Once test cases are ready, the QA team prepares the Test Data based on preconditions. The entry criteria of this phase are that the activities in test planning should be finished and the test plan should be ready. The exit criteria of this phase are that the test cases should be signed off, the test data should be ready and the test scripts prepared if automation is in scope. Test cases should be mapped with the Requirement Traceability Matrix to follow up on coverage of requirements if anything is missed. Activities in the Test Case Development Phase Following are the three activities that are carried out in the Test Case Development phase − Test Scenarios Identification Scenarios ease the testing and evaluat...
10 If you are given a new requirement, how would you go about testing this requirement? Understanding the new requirement and specification Check that all possible scenarios have been considered in the new requirement, and try to find any gaps or uncovered cases Create a new test plan according to the new requirement Try to find all ambiguities in the requirements Create a Test Plan, Test Case, Test Data for testing Uncover contradictions with other requirements and with internal and external standards See if there is a way to check whether implementation meets a requirement Industry Connect