Scenario for comparison between GF-cli and GF-app single page app

Nobody has claimed this yet.

Greetings,

As I create tutorials for my students to use your great tool, I realize how hard it is to create good scenarios for Greenframe:
- that really **emulate real usage** but without during too long,
- that last long enough to show the **whole "curve" of resource use**.

I checked all the examples from the documentation and the end-to-end tests, but none have results as general and as good as those got from GreenFrame.IO single page project.

It seems that they wait *both* for events and for fixed duration.

I tried to design such a scenario. For now it is like this:

```js
const visit = async (page) => {
await page.goto('', {
waitUntil: 'networkidle',
});
await page.waitForTimeout(10000);
await page.scrollToEnd();
await page.waitForNetworkIdle();
await page.waitForTimeout(7000);
};

module.exports = visit;
```

For a "light-impact" application, Its results (fig.1) are quite similar to GreenFrame.IO single page project's (fig.2):


But for a heavy-impact one, its results (fig.3) are still very different from GreenFrame.IO single page project's (fig.4):


Would it be possible for you to disclose your single page scenario (in place of `src/examples/visit.js` or as documentation)?

It would provide a smoother learning process and would provide a way to compare results from the Web UI single page (typically for applications done by others) and from the cli (typically for application being developed and tested locally).

Best regards.

Start with src/examples/visit.js and review the documented examples and end-to-end scenarios. Compare the event and fixed-duration waits described in the issue, then document or provide the single-page scenario so CLI results can be compared with the Web UI; done means the scenario is available for learners to use.

Written by the indexing model from the issue text.