Imagine you just build a new feature that really sums up to a single scenario: your user can say "Do a scan on Wednesdays at 10.21 every second week of the month".
To test that basic positive scenario as attended testing, you kick up a Windows machine you will test on. It just happens to be a out-of-the-box-clean US 64-bit Windows 10 with the latest OS patches all in it. You confirm that indeed there is a scan on Wednesday (as it happened to be today) at 10.21 and that it looks like it is supposed to happen again in a month. Having chosen a realistic scenario, one that a user would definitely be likely to set up, you leave the machine waiting and make a note to test again in one month, and verify there were no surprise runs in the meanwhile.
If you know something about exploratory testing, you would probably look at the basic positive scenario as a starting point, and explore a lot more around it:
- Explore Day, Time and Cadence
- Explore type of task, is "Scan" always the same thing, realizing it scans something that could be entirely different
- Explore plausible (and less plausible) error scenarios around wrong values, missing values, mixed up values, unintended use
- Explore other things that could happen on the computer simultaneously and could have an impact
- Versions of Windows for Workstations and Windows for Servers
- 64bit and 32bit - same code, different executables that only can be tested with right bitness.
- Mixes of patch level and "computer cleanliness"