Skip to main content

How test steps and Expected result and actual result should get differ each other and be unique?

Image
By
 Test steps are action-oriented and describe the registration process, the expected result outlines the desired outcomes, and the actual result provides observations on what actually occurred during the execution of the test case. 

 Each section serves a unique purpose and together forms a comprehensive test case. 
Any discrepancies between the expected and actual results can be easily identified and addressed.


Test steps, expected results, and actual results in test cases should be distinct and unique to provide clarity, avoid ambiguity, and facilitate effective communication between testers and other stakeholders. Here are some guidelines on how to make them differ and unique:


Test Steps:


1. Sequential and Clear:

• Test steps should be listed in a sequential and clear manner. 
• Each step should represent a specific action that the tester needs to perform.


2. Action-Oriented:

• Use action-oriented language in test steps. 
• Clearly state what actions the tester should take, such as clicking buttons, entering data, or navigating to specific pages.


3. Specific and Granular: 

• Break down test steps into specific and granular actions. 
• Avoid combining multiple actions within a single step to maintain clarity

Expected Result: 

1. Outcome-Focused:

• Expected results describe the expected outcome or system behaviour after performing the test steps. 
• Focus on the end result rather than the intermediate steps.


2. Align with Requirements: 

• Ensure that the expected results align with the requirements or acceptance criteria. 
• Link expected results to specific functionalities or user stories.

3. Quantifiable and Measurable: 


• Make expected results quantifiable and measurable whenever possible. 
• Use specific values, states, or conditions to clearly define success.

Actual Result: 

1. Observation and Recording:

 • Actual results describe what actually happened when the tester executed the test steps. 
• Record observations without making interpretations or conclusions.

2. Detail Deviations: 

• If there is a deviation from the expected result, provide detailed information about the observed behaviour. 
• Include error messages, unexpected outcomes, or any issues encountered.

3. Include Artifacts:

 • Attach screenshots, logs, or any relevant artifacts to support the actual results.
 • Visual evidence enhances the understanding of the observed behaviour.









 

Comments

Post a Comment

Popular posts from this blog

Had you to design test cases for a complex feature. What factors did Tester consider, and how did prioritize test scenarios?

By
  Take an instance as new application has integrated into existing applications(i,e., Running on real time )Customer want to integrate their application into third party vendors in order to let the customer order their needs through our created app itself. Factors Consisdered : Error Handling , Functional Requirements , Edge cases , Non-Functional Parameters . Transaction Flow Flow1: Customer Land on third party vendors app and start picking their items. Flow2 : Picked Items has to go Cart Page and can see number of items added by visually. Flow3: Once click to checkout , it will allow the user to input their card details and processing transaction. Flow4:Once Transactions done, newly created app show the details of the order and online tracking number . Prioritize scenerios based on the Business Emergency and needs ,well in briefly communicate to team members to identify the Critical paths and prioritize the that test suite first and Start  the execution based on what need to...
Post a Comment
Read more

Static and Non-Static

By
  What is the purpose of the static keyword in Java? The static keyword is used to declare class-level variables and methods . They belong to the class rather than instances of the class and can be accessed using the class name. can we use the static keyword for package level access? In Java, the static keyword is not used for controlling access levels. The static keyword is primarily used to define class-level members, such as variables and methods, that are associated with the class itself rather than with instances of the class. The concept of access levels, on the other hand, is controlled by access modifiers. public class MyClass {     public static int publicStaticVariable = 10;     static int packagePrivateStaticVariable = 20; // package-private by default     private static int privateStaticVariable = 30; } To summarize, while static is used to define class-level members, access modifiers (public, protected,...
Post a Comment
Read more

Headed Vs Headless Operation

By
  Headless Mode: Purpose: Headless mode refers to running the browser without a visible GUI. The browser operates in the background, and there is no actual browser window displayed. Benefits: Faster execution : Headless mode often performs faster than headed mode because it doesn't need to render the graphical user interface. This can be advantageous when running a large number of automated tests. Resource efficiency : Since there is no need to render the UI, headless mode typically consumes fewer system resources, making it more efficient, especially for running tests in environments with limited resources. Server-side and continuous integration : Headless mode is commonly used in server environments, continuous integration (CI) systems, or when running tests on servers where a graphical environment is not available. Headed Mode: Purpose: Headed mode refers to running the browser with a visible graphical user interface (GUI). You can see the browser window opening and performing a...
Post a Comment
Read more