[Jerome]

Derrick, “Intellimatch was successful’’ makes sense to me since I have a high-level understanding of the Swift [MT320 and MT940] technical process. I have the tools to check that TIBCO received an ACK back from Intellimatch and this concludes the technical process.

What I just realized right now is that business does not have these tools nor do they have a report to answer client queries:

Has my Confirmation or Statement been sent?

Can you send proof that it was successfully sent?

When was it sent?

We are reactive to business and our clients by having it in a log file that is a technical artefact. We need a report with those messages that were sent successfully and those that failed sent to business daily. This may or may not already exist in Intellimatch but it does not reach the ops support teams who are client facing. I will be making a recommendation to my team lead and request that such a report closes this gap in the near future. The end result will be that the Chameleon support team will gets fewer calls regarding this. Client facing Ops team will have the information on hand to answer such queries immediately.

Wasted time identified with a partial solution of how we can overcome it!

My other take-away from the review session … I need to have SBEs that allows my team to build the right product [for the customer] and those that get the product built right [for the developer]. I then need to use the correct language to build a common understanding when inter-acting with each.

[Jerome]

I attended Godjko’s Interactive Gherkin webinar last week, 31 August 2021.

Unfortunately, between blank examples and my knowledge gap, I got lost so I didn’t attend the 2^nd session.

I did grab a few tips on writing good SBEs:

1. keeping them short

2. obvious things are obvious to different people in different ways

3. ensure there is a common understanding of the scenario across the value stream.

4. Describe the outcome and not how to achieve it

5. Do not hard code data in the example – rather reference a data set when executing the scenario.

6. Exclude clean-up actions from scenarios

I also did a bit of reading on feature files and how they are used:

Feature

Background

Scenarios grouped with a common purpose.

Thanks to Marcus and Heidi, I configured NotePad++ with the Gherkin add-in.

I now have a feature file and I am another step closer to achieving my goal.

[Derrick]

An Aha – Now I won’t confuse the two – Build the right product for the customer vs <b style=”font-family: inherit; font-size: inherit;”>Get the product built right<b style=”font-family: inherit; font-size: inherit;”> for the developer<b style=”font-family: inherit; font-size: inherit;”>. It is also what we termed Business Facing. The developer facing is all about technical debt, change and cost of ownership. You have highlighted what it means to be a Software Quality Engineer vs a Tester. Going beyond the obvious and bringing those interventions that make for a better customer experience and lower cost of ownership. This brings meaning to the saying build quality in