Skip to content

EET for Payment Request – 2025-04-30

Today, we conducted an Ensemble Exploratory Testing (EET) session for the Payment Request feature. Although it’s a bit late in the development cycle, it was a valuable opportunity for the team to understand how EET works and to prepare for the creation of regression tests.

✅ Preparation

  1. Zak, Martin, and I first discussed team setup and agreed on a suitable time.
  2. We scheduled a 1.5-hour testing session with David and Dimitri. Feel free to invite others when planning similar sessions—people can always decline if the timing doesn’t work.
    (We highly recommend including a diverse group of team members.)
  3. Martin and Li prepared the test documentation, including a feature introduction, list of involved endpoints, and instructions for using the Postman collection.
  4. Li created a Majority user and ensured the Postman collection was functioning properly.

▶️ Session Progress

  • Brief EET knowledge refresh
  • Introduction to Payment Request testing
  • Rotating roles: Navigator, Driver, and Observer while testing

🐞 Issues Discovered

  • Unclear why an identifier is required when adding a card—it seems even a dummy identifier would suffice.
  • No real transaction is triggered in the Majority account—why? Can this be improved?
  • Error messages expose too much information when using a non-existent user identifier.
  • Deleted cards can still be used to submit transactions and can be re-added using the same cardId.
  • When the same card is added again the error message shown is vague: “Try with another card!”.

💬 Debrief Highlights

  • The EET format was engaging and helped everyone stay focused while deepening their understanding of the flows.
  • The session started slowly but gained momentum over time.
  • More team members need familiarity with Postman.
  • We should stick to having one Navigator; Observers should think actively but remain quiet.
  • Consider shorter (e.g., 1-hour) sessions held more frequently.
  • EET should occur earlier in the development cycle—ideally when just a few APIs are available—so we can “shift left” and provide earlier feedback.
  • There wasn’t enough time to explore more complex scenarios (e.g., country limitations on transfers).

🔜 Next Steps

  1. Martin will review the identified issues and begin preparing related regression tests.
  2. Li will clean up the Postman collections and share her experience with the rest of the team.

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