Page - 32 - in The Future of Software Quality Assurance

32 F. Faber DASA DevOps principle is about Customer-Centric Action [3]. Testing could help focuson thecustomerwhenyouapplycustomer-centric testing. The first step in customer-centric testing is collecting the requirements,because theywill lead to test cases. Specificationby example [13] is a term which describes a way of dealing with requirements. Another term which shares the same set of principleand ideas is Behavior-DrivenDevelopment [13, p. xiii]. Adzic writes that specifying should be done collaboratively to be most effective. In Agile, the term “The Three Amigos” started, where a business analyst, a developer, and a tester worked together on the requirements of a new feature [14]. This process reduced complexity and tried to get the broadest view on requirements with a small group. In DevOps a team draws up requirements in a collaborative manner, whereby all the team’sexpertise is considered. It takes it a step further fromTheThreeAmigos whenyoufocusontheexpertise thedifferentengineersbringina team.Thesekinds ofexpertisecanshape thequalityofyourservice. Specification by example starts with the customer perspective when writing requirements. One format for doing that is the Given-When-Then format, also known as Gherkin language [15, 16]. This way of writing down requirements in terms of behavior is a way of putting the customer in the center. It’s also a format which is much easier to understand by a customer, either internal or external. Using multiple of these statements will give a set of examples which identifies the functionalitya customerwants. It enablesdiscussionbetween the customerand the DevOps team on a level both can relate to. Examples are a way to illustrate the behaviorof a customer and these examples take requirementsa step towarda more customer-centricapproach. FromtheGiven-When-Thenformat to theactual tests isasmall step to takewith multiple test tools.Tools likeCucumber[17]makeitpossibleforengineers tomake test cases with this format. In these tools, Given, When, and Then act as keywords and can be linked to test code which is used to run the tests. Cucumber and other toolskeeptherequirementsvisible,sotheycanbepartofongoingdiscussionsonthe requirementsandtestcases. In testexecutionreporting,thesameformatcanbeused to share the results of tests to stakeholders. Teams must consider the management of the tests and gluecode in Cucumber,because it may result in a lot ofextra work if it isnotmanageable. DevOps does not demand teams to implement Specification by Example or use Cucumber as their primary test tooling. Both the method and tool are merely examples of another way of testing where the approach is to look directly at the customerwhencreatingrequirementsandtestcases. It canhelpcreateamindset for Customer-CentricTesting. 3.3 SpecializedTesting More specialized tests like security and performance testing should also be done within a team. This can potentially pose a problem, because what do you do when