The Batching Rule

When adding Welltested to an existing project, it's recommended to generate tests in the batches.

This gives Welltested the opportunity to learn your code style and any mistakes it's making and provide better subsequent results.

Batching procedure

Start out with 3 classes that are different with each other in terms of functionality and dependencies used. Fix any syntax issues in generated tests and save them to the system.

Repeat the process with 5, 7, 10 and more and you'll see that we start performing better with each iterations

💡: Initially choose classes with 1-3 methods or else add the other methods to excludeMethods to avoid manually fixing a large number of tests.

PreviousRegenerate Bad Tests NextFAQs

The Batching Rule

When adding Welltested to an existing project, it's recommended to generate tests in the batches.

This gives Welltested the opportunity to learn your code style and any mistakes it's making and provide better subsequent results.

Batching procedure

Start out with 3 classes that are different with each other in terms of functionality and dependencies used. Fix any syntax issues in generated tests and save them to the system.

Repeat the process with 5, 7, 10 and more and you'll see that we start performing better with each iterations

💡: Initially choose classes with 1-3 methods or else add the other methods to excludeMethods to avoid manually fixing a large number of tests.

PreviousRegenerate Bad Tests NextFAQs