Automation that enables your sprint delivery (in-sprint automation)

Easy creation of automation scripts that validate the business process (behaviour of system)

Going beyond automated scripts that just check the code works

A Center of Great Service for service virtualization

Reducing effort and risk in end-to-end regression testing

Delivering test data that improves the quality of code

Rapidly creating automated  reusable assets for Continuous Integration & Release Management

The Development Challenge

Feedback loops to Developers from automated regression tests can take weeks

Manual scripting for test automation is slow and cannot keep pace with sprints

Developers lack the time an expertise to improve test coverage

Test automation is a silo resulting in effective quality assuarance 

Finding the time and capability to Shift Automation Left

What we do

We build capabilities for new ways of working that transform your software delivery pipeline to a software delivery value chain

  • Build good, automated tests at the interface level, of which API is one type of interface. A good test is one that has a reasonable opportunity of finding a bug
  • Automate the DevTest assets created through the Specification-by-Example process
  • Convert Gherkin syntax files (Given When Then) to feature files for automation for both UI and API
  • Enable and enhance CI pipelines with optimal QA coverage and patterns of behaviour
  • Develops guidelines for deeper technical tests ensuring CI Unit test coverage
  • Build automated feedback loops for all stakeholders

BA, Dev, Testing, Automation

Business and Product Owners

Management

  • Design, create and supply test data at time of unit and component test execution
  • Create and maintain a SMARTT Asset Library for DevTest mapped to Application Under Test features and/or stories
  • Create an automation library of scenarios that is tightly coupled to the code under development for an instant feedback loop of feature validation (IDE or CI Server)
  • Manage and enable a high rate of change in requirements and deliverables

Tools we use

We start with what you have
  • Workflow management and Tracking System (Jira)
  • Team Collaboration Software (Confluence)
  • Gherkin ; Cucumber; PyTest, Behave, Specflow, JBehave
  • Curiosity Open Test Platform™
  • Selenium
  • Open Source API Test tools (SOAP-UI, REST Assured)
  • Commercial tools such as UFT, Parasoft, Sauce Labs, Tricentis
  • AI tools such as Eggplant and Mabl

Deliverables and Artefacts

 

 

  • Living documentation – codified knowledge that evolves with system under test.
  • SMARTT™ Asset library that supports User Acceptance Testing with automated requirement validation.
  • SMARTT™ Asset library that enables Shifting Left with Behaviour Driven Development
  • Automated reporting for business signoff

 Think of the SMARTT™ DevTest Asset Library as a library of enriched automated tests for UI and API Testing

  • Small
  • Manageable
  • Automated
  • Reusable
  • Techincal
  • Test

delivering Living Documentation linked to features in code

WHY - the value we bring

 

 

  • In providing shorter and instant feedback on the quality of code at the time of development we improve the efficiency (productivity) and effectiveness (quality) of the software delivery.
  • Reduce test cycles at the end of delivery through improved code quality at each phase of delivery
  • The library of Small Manageable Automated Reusable and Technical Tests provides a high return on the investment in automation, as the assets are used from the requirement phase through to pre-production.
  • Creates successful features that are aligned with business needs, i.e. Fit-for- Purpose functionality and an absence of flaws
  • Reduces turnaround time on bugs through shorter feedback loops
  • Increases efficiencies – due to less rework and interruptions
  • Provides and ensures traceability and alignment across Business, Development, Testing and Automation
  • Bring a testing mindset to design and build phases (including unit / component testing)
  • Understanding the impact of change by providing
    • Visibility to and validation of high-risk code execution paths
    • Visibility to and validation of associated business processes and products
  • Increased business confidence and reduced risk in production

Talk to us about "Shifting Left" with Acceptance Test Driven Development & BDD