One Page Test Plan Template

-
TEST PLAN

Let's discuss what is a Test Plan? Test Plan is a document which describes the software testing scopes and the activities needed to perform. When we say about any testing activities to be carried out there should be a proper Test plan which helps us in having insights of what can be the different approaches, scope, resources, risk  etc to have a better understand of how we can plan to test a software product.

So if incase we missed something or something goes wrong then we can refer back to the test plan document and we can identify what we have missed in the scope, testing coverage etc. This way it assist us in organising our thoughts. It helps us to better understand what is missing in the plan.

ONE PAGE TEST PLAN TEMPLATE
 
Now a days with this busy world no one has that much of time to go through any lengthy documentation. Management doesn't have that much time to read a huge document, they want to know the most important things. 

That's how One page test plan comes into picture where you can consider the important information to be included to get the most value out of it. The goal is about summarizing the testing efforts. Hence you can communicate with the reader and gather information which is absolutely required. If still there is long list you can choose the top two or three items to build the plan which fits more. But still if business needs more information you can add the links to the other document. 

Below is Dashboard format of Test plan:

Comments

Post a Comment

Popular posts from this blog

Explicit Wait, Implicit Wait, Fluent Wait in Selenium using C#

-
What are Wait commands? Waits are the command in Selenium which is very useful for the execution of the automated test scripts. During execution of automated test script, there might be some situation where issues may occur due to variations in time lag for loading web elements. In these situation Wait commands helps in troubleshooting these issues. Wait commands helps in directing a test script to pause for a certain time before throwing exception. Types of  Wait Commands Selenium WebDriver provides three types of wait commands to implement in tests. 1. Implicit Wait 2. Explicit Wait 3. Fluent Wait Implicit Wait Implicit wait directs the Selenium WebDriver to wait for a certain measure of time before throwing an exception. Once this time is set, WebDriver will wait for the webelement before throwing exception. So by implicitly wait, the WebDriver will wait for certain duration to find any webelement. This can helpful when certain elements on the webpage are not available immediately a
Read more

Assertion

-
PURPOSE OF ASSERT IN A TEST AUTOMATION SUITE  Assert plays vital role in automation testing. Without assertion we cannot provide the status of the test cases passed, failed etc. Assertion is used to validate the status of a test case. Let's take an example of a login page where a user logged in through valid username , valid password and clicking the login button. With valid credential it should login to the home page successfully. Now that a user has been logged in successfully there should be some sort of commands which helps to validate the user has successfully logged in. Hence assertion comes into picture, where we can use assertion command to validate whether the user has been successfully logged in by comparing any text in the homepage with the text provided in the command. eg. Assert.assertEquals(expected, actual) Here if the actual and expected matches , then the test case will be marked as a passed.
Read more

CI/CD Pipelines & DevOps

-
Image
CI/CD Pipelines & DevOps A CI/CD Pipeline implementation, or Continuous Integration/Continuous Deployment, is the backbone of the modern DevOps environment. It bridges the gap between development and operations teams by automating the building, testing, and deployment of applications. CI/CD is o ne of the best practices for DevOps teams to implement . It is also an  agile methodology  best practice, as it enables software development teams to focus on meeting business requirements, code quality, and security because deployment steps are automated. Before moving onto the CI/CD pipeline, let's start by understanding DevOps. DevOps is a software development approach which involves continuous development, continuous testing, continuous integration, continuous deployment, and continuous monitoring of the software throughout its development lifecycle. Let us now look at the DevOps lifecycle and explore how it is related to the software development stages.
Read more