Quality Engineering in  your IDE

QA and Test Automation that supports and enables what you do

Connecting your code to SWIFT and external code

 

A Center of Great Service to deliver Executable Specifications for Continuous Integration

Creating Smart Assets for the automation of quality assurance and testing in Continuous Build and Continuous Integration

The Development Challenge

How do you know when your code is good enough?

How do you build quality in?

Where do you find the time to build, maintain and fix code AND create reusable unit tests?

What we do

create the connections and artefacts that support your software delivery process
  • Enables orchestration of your CI Server with Executable Specs
  • Uses data from Testing the Story (Specification_by_Example process) for Enriched Unit tests that are integrated into your CI process to run the right tests at the right time
  • Generates Integrated Unit tests utilising Specification_by_Example
  • Creates and maintains your Smart DevTest Asset Library
  • Develops guidelines for deeper technical tests ensuring CI Unit test coverage
  • Integrates into your IDE
  • Contributes to regression testing pack

Tools we use

 

 

  • Integrated Developer Environment
  • Test Management Tool (such as Jira or Mercury QC)
  • Service Virtualization for New Payment Platform ISO 20022 messages and conversations
  • Using a client’s choice of Executable Specification
    • Java
    • Ruby
    • C #
    • JUnit / NUnit

 

 

Deliverables and Artefacts

 

 

  • Smart DevTest Asset Library mapped to Application Under Test features and/or stories
  • Enriched Unit tests that are integrated into your CI process to run the right tests at the right time
  • Test Data

Think of a Smart DevTest Asset Library as enriched Unit Tests for API Testing.

  • Automated
  • Reusable
  • Living Documentation

WHY - the value we bring

 

 

Executable Specifications provide:

  • Enablement of “Shift-Left” and Test Driven Development Approaches
  • High-risk code execution paths / code are tested
  • Immediate test coverage of new features
  • Raising the quality with less effort
  • “Living” documentation – code and specification