The number of possible test cases we can write and run is too long to list, but you can generally think about them in two categories:
Client-side performance tests. These are measuring the rendering time of individual components or whole pages and how long communication with the server takes. For example, asserting that a data table re-sorts in less than 100 ms.
Load and stress tests. These are usually server-side tests to see how back-end systems behave when multiple clients act on it concurrently and for prolonged periods of time. For example, assert that 5,000 users can initiate a video stream simultaneously without an impact on the user experience.
In both cases, our QA engineers work with you to design test cases and traffic patterns that you want to observe. As with all of our tests, we run them, investigate the failures, repair broken tests, and file bug reports. If you have a specific test case in mind, schedule a call and let’s discuss it.
Our parallelization infrastructure spins up a separate docker instance for each “user” and orchestrates their activity. The traffic can be programmed to complete a workflow, or a single action, depending on the test. The traffic can be generated from any geo location, on any browser, and in any volume — mix and match if you want to replicate your real world userbase.
As long as it’s measurable we can make an assertion and pass or fail a test accordingly. The most common metrics we test come from the Web Vitals Initiative, including Time to First Byte (TTFB), First Contentful Paint (FCP), and Total Blocking Time (TBT).
Definitely, we support seamless integrations with GitHub and GitLab, ensuring our testing services mesh perfectly with your continuous integration and deployment workflows. We can also work closely with your team to customize for any other SCM provider.
Yes we do. The Playwright framework can emulate more than 100 desktop and mobile devices so we can test your web application across any breakpoints that you use.