SAP Testing

How does SAP testing differ from other types of testing?

  • SAP solutions are heavily modularised. Components on their own are rarely tested, so the whole solution is usually required and testing is usually focused on validating end-to-end processes and procedures
  • SAP solutions are heavily configurable. Configuration testing always requires a risk based approach as the number of variables and permutations to cover are two vast. In general, SAP testing wants to get to the state where the GO-LIVE configuration is frozen as quickly as possible.

We can provide you with specialists to perform a review of your SAP landscapes and carry out regular patch upgrades / enhancement pack upgrades at least once a year to address any potential security issues. A big upheaval for clients but we can guide them through what should be tested. This has the benefits that we will take away the hassle and guide them through the upgrade process and their SAP system stay on the correct patch levels.

SAP and Non-SAP integration

  • Both worlds have start and end point and testing should validate those first – i.e. call it system testing.
  • NON SAP systems (legacy) should have changes kept to a minimum so that the focus can be on the SAP testing, which has a high risk of errors.
  • The earliest testing should focus on the integration points, first from an operability perspective (i.e. it works) and then from a requirements perspective.
  • E2E testing should pre-define the NON SAP depth (or cut-off points) as legacy systems tend to be much harder to change and test the deeper you go into them

SAP testing approach considerations

  • Will the business and IT requirements be covered
  • Will the configuration be sufficiently covered
  • Will the business and IT processes and procedures be sufficiently covered
  • Will the integration points be sufficiently covered
  • Will the modules be sufficiently covered
  • Will the reference data be sufficiently covered
  • Will testing support the training and implementation approaches
  • In addition, there are certain SAP modules, which are more complex than others and at higher risk of errors (i.e Security)
  • Contract Python Django Developer

    £400 - £450


  • 2 x .Net Developers

    £40,000 - £45,000 per annum + benefits

    Crewe, Cheshire

  • Fullstack Developer - Python, Django, HTML, CSS, JavaScript

    £65,000 - £75,000 per annum plus benefits, bonus & equity


  • Java Developer - Kafka, distributed & messaging systems

    £50,000 - £70,000 per annum + bonus & benefits