what is the difference between Use Case and Test Case ?
Use Case: Use case is a pictorial representation of client requirements. It is prepared by Business Analyst. In Software Engineering, Use case shows the series of actions and interaction between the user and the system to achieve a goal. It is technique to capture the business and user requirements related to system functions. The main purpose of Use case is to tell the development team what the customer wants from the system or what the customer expect the system to do. Use cases are only designed, they are not executed. Use case diagrams are derived from Business Requirement Specification. It describes the flow of events in the application. Finally, we can say that Use case plays an important role in Software Development because it tells the story of the user. The business requirements of the client are clearly showing with the help of this. It shows step by step interaction of the user with the system.
Test Case: Test Case verifies the functionality means it is as per the instructions mentioned in the use case or not. Test Cases are part of Test Scenario. We are using Test Conditions to verify the Test Case. Test Case are prepared by Test Engineers. Test cases are designed and later executed. We documented the test cases in the Excel sheets. The main goal of an Test Case is to check whether the instructions as per the use case.
What is test design and test execution?
Test Design: Test design is a way to check the outcomes of the software. In other words, we can say that creating a set of inputs for software to perform on. To ensure the outcomes which are coming are as per inputs given to the software.
Test Execution: Test Execution is performed after test have been designed properly. The outcomes of the text execution can be positive or negative. Test execution tells the Tester that whether the proposed outcome is according to the given input to the system. Test Execution evaluates the system is working properly or not.
Which phase of SDLC we write test case?
Test cases are written at the end of the coding phase. When Developers are doing coding at that time Testers do prepare their Test Cases. So, that as soon as they get the software coding from the Developers then they can start work on testing the software without wasting the time on preparing it.
Test Plan
Test plan is a document which is prepared by Software Tester. It explains the strategy to be follow while doing testing. Test plan is to ensure the delivered product is as per requirements of the user or not. It covers the details like, the estimate time to finish the testing, Who will do each task, test environment , test design techniques, features to be tested and testing tasks. Finally, The main purpose is to describe the scope, approach of the Software.
Test Condition
Test Condition is a way to check the functionality of the application. In other words, we can say that it has a set of test cases to verify the outcome of an feature of application. We can perform multiple test conditions on single feature. For example if we are taking the Login Page of an application to test.
Then we have test condition like, To check the entered username is correct or not, Entered password is correct or not, Both fields are entered or not, Blank entries and so on. These all are test conditions that we can perform on test case to verify the Login Page.
Test Case
Test case is a way to evaluate the application. Test case is set of condition that the Testers are performed to check the functionality of the application. It also helps to find out the errors in the application. Tester have to carefully design the test cases so that it can cover the whole functionality of an application.
Defect Management
Defect Management is process in which Software testers track the defects in the application. The defects which are present from the start of the application to the end testers need to logged into Defect Log file with the details of where they find the defect and the after inspection their status in the Log report. In simple terms, we can say that it is a process to detect the defects and inspect the defects from the application while developing.
Fields in Bug Report
Bug report contains the information about the bugs which testers found them while they performed testing. It contains the history of an bug while it is inspected and fixed it. It contain following fields in their report.
Bug Name: While clicking on Update button application crashes.
Description: The user data is not updating while clicking on update button
Build Version: Version Number
Reason: Defect
Date: Date on which bug reported on
Assigned To: Developer Name
Reported By: Your Name
Priority: High/Low/Medium or 1
Severity: High/Low/Medium or 1
Area Path: Menu –>Update
Bug ID: It is automatically created by bug tracking tool while you save the bug
Functional Document v/s Business Document
Functional document contains the information about functions of an application or you can say the it describes the functionality of an application. while on the other hand, Business document contains information about the business requirements and user requirements. Functional document describes the features and events information while business document describes story told by client to an Business Analyst. Business document is prepared by Business Analyst. Business document can be better explain in pictorial representation by the help of use case diagrams. Functional document focuses on what functionality customer wants from the application.
What are Locators in Salenium?
Locators are used to interact with the elements of the web page. For instance, if we are want to interact with the Text Field of the web Page then we can do this one in numerous way. Here are the list of Locators.
- ID
- Name
- XPATH
- CSS
- DOM
- LINK
- IDENTIFIER
I can show you with one simple example with the help of Facebook Website.
Suppose, we are going to check the Username and Password field of Facebook website.
I am going to use XPATH locator to find the text boxes in the web page
Firslty, you have to find the XPATH from webpage by using inspect elements then you have to write following code into your Salenium program.
IWebElement username = driver.FindElements(By.XPATH(“your XPATH which you copied from web page”);
That is all about with the help of XPATH. Rest of them all are same but sometimes you have to change some coding.