Quality Engineering your Continuous Integration workflow
Connecting your CI server to a virtualised application test gateway
QA and Test Automation that makes your feature team efficient in delivering quality code

Eliminating waste
Improving quality of code to SIT
Continuously building quality into your CD pipeline through automation
Ensuring software is in a testable state
The Development Challenge
Automation of external system test m
Time and effort to create and maintain quality in Continuous Integration
Length of feedback loop between the build and testing
Knowing what to test and when
Finding tests for changed code – even if you wrote the code yourself
Removing extraneous elements to get immediate feedback on the quality of the code under build
What we do
create the connections and artefacts that support your software delivery process
- Build a set of quality criteria for Continuous Integration and Continuous Build. These criteria are fast tracked using our knowledge base of testing criteria for payment solutions and networks (such as SWIFT and EMV)
- Evaluate, document and communicate environment and data requirements per feature
- Provide known, clean and fit for purpose test data set
- Configure your Test Gateway for integration unit tests and build acceptance tests (executable specification)
- Create automated, integration unit and build acceptance tests
- Tighten the feedback loop to the Developer regarding test results and reasons for failures
- Enable interface testing at 2 levels:
- Application and Database
- Application and dependent systems.
Tools we use
We start with what you have
- Cucumber for Executable Specifications.
- Service Virtualization tool for Service Virtualization of external application messages (Greenhat, Lisa, Parasoft, STEP)
- Workflow management and tracking system (typically Jira)
- Team Collaboration Software (typically Confluence)
- Your Test Automation Library.
Deliverables and Artefacts
- Relevant and maintainable automated test artefacts in a test library
- Dev/Test feedback loops
- Checklists.
WHY - the value we bring
- Reduces turnaround time on bugs through shorter feedback loops
- Increases efficiencies – due to less rework and interruptions
- Make sure the “new shiny” does not break anything
- Higher quality and fit for purpose code exiting the coding phase
- Happier and calmer work environment.
Let's talk about "Shifting Left" with Continuous Build & Integration
DevOps Personal Success Plan in action
An example of how value mapping is applied in the context of DevOps. Told as a story of a Quality Intervention for a feature team. This is a “live” example and represents the average situation we encounter.
I will get to that as soon as I have this code live
An example of how value mapping is applied in the context of DevOps. Told as a story of a Quality Intervention for a feature team. This is a “live” example and represents the average situation we encounter.