Structured Test Strategy Series - Day 2

By -

The Project Environment in HTSM refers to the external factors, limitations, and context in which the product is developed and tested. Understanding this can help to set realistic expectations, prioritise the tests, and identify key areas where constraints might affect the testing.


Mnemonic: MID-TEST-D. (Remember MID STD')

M: Mission

I: Information

D: Developer Relations

T: Test Team

E: Equipment & Tools

S: Schedule

T: Test Items

D: Deliverables


Example Application: Adding Products to Shopping Basket

Using this model for the “Add to Basket” feature on an e-commerce platform:

  • Mission: Confirm the feature’s functionality and reliability under various conditions (e.g., adding different items, adjusting quantities).

  • Information: Gather user stories, past issues with cart functionality, and common customer complaints about similar features.

  • Developer Relations: Check in with developers about any known complexities in the “Add to Basket” code.

  • Test Team: Leverage team members experienced in UI/UX testing to assess how intuitive and responsive the “Add to Basket” interaction feels.

  • Equipment & Tools: Ensure access to browser compatibility testing tools to test the feature across devices and browsers.

  • Schedule: Begin functional testing once the feature is stable, leaving load and performance testing for later builds.

  • Test Items: Confirm availability of the feature in the testing environment; check if it requires third-party integrations.

  • Deliverables: Plan to document test results in a test report and provide summaries in team meetings for quick insights.


    • How to Apply Project Environment at Each Agile Stage:

    • Sprint Planning: Define Mission, Information, and Schedule.
    • Daily Stand-ups: Focus on Developer Relations, Test Team, and Equipment.
    • During Testing: Concentrate on Test Items and follow the set Schedule.
    • Sprint Review and Retrospective: Deliverables are shared, and feedback on the Project Environment approach is gathered for future sprints.
    Location: Hyderabad, Telangana, India

    Popular Posts

    JMeter Producing Error: Windows RegCreateKeyEx(...) returned error code 5

    By -
    After running JMeter.bat on Command Line, Problem java.util.prefs.WindowsPreferences <init> WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5. Cause Environment Resolving the problem The error occurs because java.util.prefs.WindowsPreferences is trying to save information in HKEY_LOCAL_MACHINE\Software\JavaSoft\Prefs instead of under HKEY_CURRENT_USER\Software\JavaSoft\Prefs. Windows 7 64-bit The work around is to Open JMeter.bat file as the administrator and so it creates the key HKEY_LOCAL_MACHINE\Software\JavaSoft\Prefs.
    Read more

    Understanding about Contract Testing

    By -
    Image
    Yesterday Morning (9th May 2020), I had good discussion with  Sundaresan  Krishnaswami on " Contract Testing ". I thank  Sundaresan   for his time and sharing his knowledge. It started with an example: The Owner provides the house or Place of Residence to the Tenants. "Rent Agreement" is provided for the house and It contains agreement to use the house. The house comes with like kitchen, living room, bed room, fans, geysers etc.. It also contains who resides and what is the contractual period, obligation (money) etc.. Here, Owner is the Server and Tenant is Client.                                         Client-Server Architecture. Illustrating the same in the E-Commerce Context: In Some Development Companies, There can be two teams developing the Payments and Orders APIs. In B2B or B2C Ecommerce applications, we place an order using web browser through payment methods...
    Read more