Skip to content

EET for Phone Plan 2025-02-18

Yesterday, we had our first ensemble exploratory testing (EET) session for the Phone Plan feature, as you may already know. I’m sharing the full process here with the team—hope you find it useful!
Preparation:

  1. Lars and I first discussed the Phone Plan background and its API endpoints using Swagger.
  2. We scheduled a one-hour test session with Magnus and Gowtham. Feel free to invite others when you try—people can always decline if the timing doesn’t work for them. (We didn’t invite the Product Manager since he’s in the U.S.)
  3. Lars created the test documentation, including prerequisites and API call sequences. He also imported the Swagger API collection into Postman so we could run tests easily.
  4. I created a user from the regression tests, generated an IMEI, and ran the GET Phone Plan endpoint to verify functionality.

Session Progress:

  • Quick EET knowledge refresh
  • Intro to Phone Plan testing
  • Rotated roles between Navigator, Driver, and Observer while running the tests

Debrief Meeting:

  • The EET was engaging and helped everyone focus while gaining a deeper understanding of the feature.
  • We discovered an issue where the Change Plan feature didn’t work as expected.
  • Observers (like me😅) had to be reminded not to jump in too much!
  • Four or five people is a good number, so there is not too long wait time for people to take an active role.

Next Steps:

  1. Lars identifies the reason of  Change Plan issue and will discuss with the product manager.
  2. Li reorganizes the tested endpoints into specific scenarios in Postman collection.
  3. We’ll conduct deeper negative case testing in the next session.

Let me know if you have any thoughts or suggestions! 🚀