In this lecture, you will learn how to properly onboard your project with TestChimp, connecting the code repo, setting up plans folder, and getting test folder scaffold setup so your code agents can execute testing after each PR.

First - signup for a free trial at TestChimp.

You can use the linked sample code repo - fork the repo and use it as a playground for integration with TestChimp.

TestChimp orchestrates QA workflows to be executed by your Agents. This is enabled by installing and configuring TestChimp SKILL on your preferred agent (cursor / claude etc.).

This lecture will guide through how to install and configure the agent, covering key areas such as environment provisioning, TrueCoverage setup, and resolving common configuration gotchas.

In this video, you will learn how to execute the "/testchimp test" workflow that authors tests for your PRs.

First - consider a sample feature (such as "ability to add a coupon code to orders" - if you are following the sample code repo - which is a food ordering webapp). Add a few stories / scenarios via TestChimp platform, sync them to code repo you forked.

Then create a branch and implement the functionality. 

Afterwards, run the "/testchimp test" command on your agent to execute the testing workflow for the PR.

TrueCoverage brings test traceability to real user behaviour. This unlocks powerful capabilities that enables your agents to understand what user segments are present, what they do in production environment, the different user journeys and variations and the various metrics (such as frequency, funnel position, drop-off points) - which can then be used for ensuring business critical journeys, segments, variations are covered in testing.

Unlike requirement traceability, this provides real data backed stronger guarantees of coverage.

Scripts capture functional regressions in your apps. But that is just half the battle. Your app can be "functionally" working, yet be completely unusable if it is riddled with UX bugs - such as broken layouts, accessibility issues, visual glitches, performance issues, usability bugs etc.

Usually, this required human intervention - and teams either had to hire manual testers or skip entirely. Learn how to run analytics agents that walk through your app - guided by your E2E tests, catches UX bugs and tracks them, aligned with your app structure.

Often, some amount of manual testing would be present in typical QA setups due to following reasons:

1. Legacy test scenarios that are yet to be automated

2. Features still under active development / likely to churn

3. Scenarios for which some external dependencies that make automation too cumbersome than doing a manual check

However, when it comes to executive overview of coverage, you need complete picture - across both manual and automated testing. This requires carrying out manual testing with requirement traceability.

In this lecture, you will learn how to use the TestChimp Chrome extension companion to carry out manual testing with requirement traceability linking, as well as report bugs directly from the extension, capturing screenshots and referring areas in the screen where the issue is happening.