Skip to main content

Essential of Creating Test plan in Testing

Image
By

 

Why Test Plan is Vital Document!

Test Planning process and plan itself serve as vehicle for communicating with other members of the project team, tester, Dev, BA, Peer and other stakeholders. This communication allows the test plan to influence the project team and allows the project team to influence the test plan.

We can accomplish this Communication through circulation of one or more test plan drafts and through review meeting.

E.g.: Please tell me what the plan is for releasing the test items into the test lab for each cycle of test execution

E.g.: Please let me know which version of the test tool  will be used for the regression tests of the previous increment.

A test plan Document becomes the record of previous discussions and agreements.

Test Plan helps us to Manage the change if you are in Agile , have to this as Handy.


Ways to write a Test Plan Document.

  1. Analyze the Product:
    • Understand the product's objectives, target users, specifications, and functionality.
    • Conduct interviews with stakeholders to gather requirements and expectations.
    • Perform a walkthrough of the product to identify key features and components.
    • Identify Project Risk and Product Risk
  2. Design the Test Strategy:
    • Define the scope of testing, including what will be tested and any exclusion criteria.
    • Determine the types of testing to be conducted (e.g., functional, usability, performance).
    • Identify potential risks and issues that may impact testing.
    • Assign roles and responsibilities to team members involved in testing.
  3. Define Test Objectives:
    • Clearly state the goals and expected outcomes of the testing process.
    • List software features and functionalities to be tested.
    • Specify performance standards and acceptance criteria for each feature.
  4. Define Test Criteria:
    • Establish criteria for suspending tests if certain conditions are met (suspension criteria).
    • Define criteria for determining when testing can be considered complete (exit criteria).
  5. Resource Planning:
    • Identify and allocate human resources, including testers, developers, and any additional support staff.
    • Determine hardware and software requirements for testing, including tools and environments.
  6. Plan Test Environment:
    • Set up test environments that mirror the production environment as closely as possible.
    • Ensure access to real devices, browsers, and operating systems for comprehensive testing.
    • Consider factors like scalability, security, and data privacy in the test environment setup.
  7. Schedule and Estimation:
    • Break down testing tasks into smaller, manageable units.
    • Estimate time and effort required for each task, considering dependencies and resource availability.
    • Create a project schedule with milestones and deadlines for completing testing activities.
  8. Determine Test Deliverables:
    • Identify the documents, reports, and artifacts to be produced during testing (e.g., test plans, test cases, defect reports).
    • Determine any tools or equipment needed to support testing activities.
    • Ensure proper documentation and communication of test results and findings.

Why Test strategy Into Test Planning?

  1. Consistency and Standardization: Integrating the test strategy into the test plan promotes consistency and standardization across testing activities. It ensures that all team members are working towards common objectives and following established methodologies, leading to more reliable and reproducible results.
  2. Communication and Collaboration: Involving the test strategy in the test planning process facilitates communication and collaboration among stakeholders involved in testing. It provides a shared understanding of the testing approach and ensures that everyone is working towards a common goal.

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

Pre conditions and Post conditions in Test Ng.

By
Pre conditions and PostConditions in Test Ng. Vision of Preconditions and Postconditions: 👉 Ensuring Test Isolation: By using preconditions and postconditions, you ensure that each test method is executed in isolation, with a clean and consistent state. 👉Promoting Reusability: Setup and teardown tasks defined in preconditions and postconditions can be reused across multiple test methods, promoting code reuse and reducing redundancy. 👉Maintainability: Clearly defined preconditions and postconditions enhance the maintainability of test code. Changes or additions to the setup and cleanup logic can be made centrally in these annotated methods. TestNG PreConditions and PostConditions flow.   Before Suite (once) Before Test (once for each <test> in the suite) Before Class (once for each class with test methods in the <test> ) Before Method (before each test method) Test method execution After Method (after each test method) After Class (after all test methods in ...
Post a Comment
Read more