Why Testerum?

The short version is that we can make your life easier while saving you money. How do we do this?

• by bringing clarity on your requirements
• letting you sleep easy at night knowing that all your functionalities are end to end tested
• allowing your testing team to create tests in a very easy manner, without programming knowledge
• programmers do not need to create and maintain a testing platform
• your documentation will be always up-to-date
• we have integrations with all the major technologies which allow you to test your platform in isolation
• out-of-the box solution
• the easiest way to test your REST API
• tests are versioned with your code
• integrate your test suite in any CI/CD environment

What can you do using Testerum?

• define your acceptance criteria and use them as manual tests
• test your REST API
• test your Web Applications (Selenium)
• initialize and verify any Relational Database
• mock your application 3rd party API calls
• execute all your tests in any CI/CD environment
• fully extensible platform. You can create any custom integration you want in an easy manner.
• clear reports regarding quality, stability and progress of your project
• trigger the tests execution from a Docker container

In the end, Testerum can cut the costs of your project by 30% and can make the difference between failure and success.

For Product Owner

• can define the expected functionalities and acceptance criteria
• can check how much of his project was implemented
• can asses the quality of project implementation

For Testing Team

• creates tests in a visual way
• creates quality tests
  • each test should be independent from other tests
  • initialize the project data source (DB, files, 3rd party API, etc) using a simple friendly UI
  • the application under tested can be run in complete isolation
• created tests are easy to read and understand, that means easy-to-maintain tests
• no programming skills are required
• a tool that with a small learning
• Manual and Automated tests under one tool
• Acceptance Criteria that are not automatized can be used as Manual Tests
• out-of-the box tool, no more dependency on the development team

For Development Team

• doesn't have to spend time to implement a testing infrastructure
• benefits from a testing platform with many technologies integrations
• can create custom integrations
• can integrate & run the tests in any CI/CD environment
• can run the tests from their favorite IDE
• tests are versioned with the code
• tests' details are easy to find and understand

Prebuilt integrations in Testerum

• Initialize any Relational Databases (MySql, PostgreSQL, Microsoft SQL Server, Oracle, H2, etc.)
• Verify any Relational Database (MySql, PostgreSQL, Microsoft SQL Server, Oracle, H2, etc.)
• HTTP Mock. An easy way to mock all your application 3rd party HTTP calls
• HTTP Request.
• HTTP Response Verify. Makes REST API testing very easy.
• Web UI testing based on Selenium
• File System

Integrations that will come soon

• iOS
• Android
• NoSql Db: MongoDB, Cassandra, Redis, HBase, Neo4j, DynamoDB, etc
• ElasticSearch & SOLR
• Kafka
• Docker(now available!)

Reality Check

From our experience everybody talks about Test Automation, everybody wants to do it, and more then 90% of the teams fail in having an acceptable level of test automation.
Most of the time these things happen because:

• developers don't have the time to set up and maintain a proper testing infrastructure.
  A good testing infrastructure can take up to 30% of all the development time.
  
• testers are not developers. Most of the time, the testing infrastructure is made by aggregating different open source testing frameworks. This approach forces the testing team to write their tests in a programming language. Most of the time, testers have some programming skills but to maintain a testing infrastructure written in a programming language is challenging even for the development team. In time, your team will spend more time in maintaining the infrastructure than on creating more tests scenarios, your team will lose the trust in the tests and they will abandon them.
• tests written in a programming language are hard to maintain.
• tests can't be used as documentation. Most of the time, even in BDD, tests do not reflect the acceptance criteria and most of the time is impossible to use them to understand the requirements for a particular functionality.
• tests are not interdependent.
• tests fail to completely isolate the tested project