How I started using HTSM for my testing

 How I started using HTSM for my testing  


 When I initially learned about it, it sounded really technical and alien. I had to read this document, several times to fully grasp it.  


 The HTSM (v.5.9) is a set of guide-word heuristics designed to help you think better about test strategy. It includes four focus areas: test techniques, project elements, product elements, and quality criteria categories.


  When I was given a new project at my work, I found this at the perfect time. My typical approach to performing an initial spec analysis was to start with test cases. Then rewriting again in the midway, then again, because it was messy.   I was writing functional tests based on the functionality, then would go to UI tests. While doing that I'd get some test ideas from the expected behavior, I'd switch here then. I wasn't following any structure or plan.


  At that time I was getting training from Ajay Balamurugadas, he assigned me the project of using HTSM principles for Google Docs.  I also referred his article while exercising.  This improved my understanding.


 I then returned to my current work project. This time, the flow is more organized. This is how:

     I started by gathering data about the Project Environment. The goal or mission, the team, and details about the product being tested (Dev, test, XF), Tools (Automation, Bug tracking, communication, test management), timeline (Test design, data creation, XF activity..), Test items (in scope, out-of scope, product availability..), Deliverables (Test plan, test scenarios,  defect report, test progress report, communication medium..) etc..


The above I presented as a Test plan, along with high level use cases and mind map of expected results.


 The next section was Product Elements, which were grouped (SFDIPOT) by special elements to be taken into account for test strategy. Before starting work, I also viewed Product Coverage Outline - YouTube. Having a better idea now, I was ready to start. I had also used a mind mapping tool to ease my learning of google Doc’s product elements.



 I began working on my official project after spending a few hours learning how to utilize HTSM's Product components learning technique. This time, I was much clearer, and I made another mind map for myself as a reference. I felt like I had a good coverage with that in hand. 


I'm now learning XMIND software using HTSM. Until I can use HTSM naturally, I'll practice with more applications.

Comments

Post a Comment

Popular posts from this blog

API Testing journey

  API Testing journey   I've been working on learning API testing for quite some time. I was only aware of the acronym API, which stands for application programming interface, until 2022. I started my search on Google because I wanted to learn more than that.  I Completed the following courses on various education platforms: 1. Coursera — Postman - Intro to APIs (without coding) 2. Coursera — Start Your API Testing Journey With Postman Tool 3. Udemy —  REST APIs with Postman for Absolute Beginners 4.  MOT - https://github.com/g33klady/TodoApiSample/tree/main/Resources . https://github.com/g33klady/TodoApiSample 5. LinkedIn Learning — API Testing Foundations 6. Test Automation university: https://testautomationu.applitools.com/exploring-service-apis-through-test-automation / 7. Test Automation university: https://testautomationu.applitools.com/python-api-testing /    Postman was discussed as a tool for API testing in the first three courses. In order to test an API endpoint, I
Read more
  Observation: How it has helped me as a tester? In one of the chapters of her book, "Explore IT," Elizabeth Hendrickson discusses observation and how it is crucial for exploratory testing. Checking logs for surprises is one technique to observe during testing. I was brought back to my days as a mid-level test engineer while reading it. On the user's side, the product appeared to be relatively straightforward, but it actually had a sophisticated architecture and a lot of moving components. For this product, there were very few user interactions; everything took place in the background, and logs were essential for troubleshooting. When I first discovered a bug, I would gather proof—reproducing steps, error logs—most often grep 'error' log files—and screenshots—and be prepared to report the issue. My manager would ping me with questions like, "Did you try to reproduce the bug in another test combination?" and "Did you check that?" and “Did you tr
Read more

My first time attending a software launch party

Image
  Postman celebrated the introduction of Postman Flows this week in San Francisco, on August 16th 2023. Following the release of Postman Flows a few months ago, Beth Marshall posted a YouTube video explaining how testers might use it for API testing procedures.   Ever since I started my API testing journey, I've been watching for Postman's announcements, challenges, You Tube Live sessions, and demonstrations. So I made the decision to go to this event as well.    When I arrived , Postman Flow was being used to welcome every registered guest. My name flashed on the welcome board when I clicked Run on their flow they had created after signing in (I forgot to take a picture of it). Greetings flow Two customers demonstrated how they are utilizing Flows to address issues and open up new possibilities. One of them includes a flow designed specifically for integration testing.   I was able to use Flows to design my very own, uniquely branded Postman YETI and select the swag I wanted (
Read more