> For the complete documentation index, see [llms.txt](https://bt-studio.gitbook.io/bestest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bt-studio.gitbook.io/bestest/test-management/test-cycles/create-cycles-101.md).
# Create cycles 101
Cycles can have deep complexity on creation, based on your app's complexity, and volume of testing need. Let's see few examples, and how that should be set up in BesTest.
## Few testcases - occasionally execution
{% hint style="info" %}
For small teams, or new products. Having few tests is really cost effective.
{% endhint %}
Create a cycle, select your test cases using folders, and start executing them.
## Many testcases - non-deterministic execution scope
{% hint style="info" %}
For exploratory and non-governed sessions. Powerful BQL filters can find any testcases.
{% endhint %}
Select testcases with combination of folders and filters. You can do multiple filtering and add what selected.
## Testing against Requirements
{% hint style="info" %}
For covering new and old features, without being an expert in testcase selection.
{% endhint %}
Make sure your requirements have test case coverage, then create a cycle and simply select the Requirements you need to test.
The requirements are being resolved to test cases on the planning tab.
## Regression scope, with new features
{% hint style="info" %}
Release testing new features in mature products.
{% endhint %}
Adding new features to a bigger functionality pool, is always risky. You want to cover the
* regression - existing features remain working features
* new features - deep testing on what has been added
* anything else, release specific
How to cover this:
1. Create a (or multiple) collection for the Regression scope, and start with that. You can use folder rules in Collections so they remain always up-to-date.
2. Select the new requirements, which are just being made and covered by the team. The related test cases will be added to the cycle
3. Check if any more test cases need to be added.
Planning tab deduplicating testcases in the following priority order: Directly added, via Requirements, via Collections.
## Module based complex testing scenarios
{% hint style="info" %}
Enterprise scaling, for distributed testing teams with per module responsibility.
{% endhint %}
Build huge test cycles in seconds, using well configured collections. Collections are really flexible to define - even dynamic - testing scopes.
