Testgram is a new way of testing web applications using artificial intelligence.
We take a very different approach to testing. Testgram differs from traditional testing in two key ways:
- Testgram tests through simulated users, not scripts. We use data-driven simulations as a way to test your web application. In Testgram we help you design and simulate real user behavior as the primary lever to ensure quality. This is important because it allows us to bring real user voices and experiences to the core of how we test our software.
- Testgram tests the critical paths in your application. There are no assertions in Testgram. When you build a Player, Testgram builds a baseline understanding of the impactful set of paths that your users take when interacting with your application. When you simulate, these Players mimic real user journies in new environments to ensure your application is working correctly.
Everything in our platform is built to help you easily create and deploy these simulations. In the end, our goal is to help you build confidence in your code through early detection.
Testgram is Simple
The magic of Testgram is simple. We don't use scripts in the background. We use real usage data.
Testgram looks really different from many testing tools you may be used to. To understand Testgram, here are some core concepts you'll need to know.
Your World naturally changes over time as new pages, elements, or features get introduced. Testgram keeps up with your World through the data it collects.
In a video game, players are used to complete tasks and conquer levels.
Players can be simulated on any environment, and fail if they cannot execute their checkpoints.
One or more Players run a Simulation. Running a simulation often looks like running
tg sim @<player_name> in your command line.
Simulations can run anywhere: from your local machine to CI pipelines and QA environments.
Testgram is a very different way of testing. The way we create a 'test', run a 'test', and get feedback looks very different in Testgram.
- We collect data to learn your World. The World keeps learning your application and adjusts as changes are made.
- Instead of writing a test, you create a Player. Players run multiple tests based off their goals.
- Instead of running a test, you run a Simulation. Simulations are based on real user behavior and not a user story or assumed interactions.