use api tests or web to get ideas how to stress the system

docs/ocis/development/beta-testplan.md

@@ -11,6 +11,9 @@ geekdocFilePath: beta-testplan.md
 
 This document is supposed to give you some ideas how and what to test on ocis. It's not ment to be an extensive list of all tests to be done, rather it should help you, as beta-tester, to get started and enable you to get creative and create own test-cases. [Derive from these examples, be creative, do unusual and unconventional things, to try to break things](https://twitter.com/sempf/status/514473420277694465).
 
+One option to create new test-cases and to stress the system is to examine what the [API acceptance-tests](https://owncloud.dev/ocis/development/testing/#testing-with-test-suite-natively-installed) or the [web-UI](#web) does, [examine the requests](#
+decode-https-traffic-with-wireshark) and do something a bit different with curl. This is also a good way to find out how APIs work that are not already fully documented.
+
 Some cases have suggested setup steps, but feel free to use other setups. This can include:
 - different deployment methods (e.g. running compiled binary, docker-container, docker-compose setup)
 - different identity managers (e.g. different external LDAP, internal IDM) **TODO documentation link**
@@ -222,6 +225,7 @@ To decode the HTTPS traffic we need the keys that were used to encrypt the traff
    - curl: `SSLKEYLOGFILE=/tmp/sslkey.log curl -k -u admin:admin https://localhost:9200/ocs/v1.php/cloud/users`
    - Browser: `SSLKEYLOGFILE=/tmp/sslkey.log firefox`
    - LibreOffice: `SSLKEYLOGFILE=/tmp/sslkey.log libreoffice`
+   - acceptance tests: `SSLKEYLOGFILE=/tmp/sslkey.log make test-acceptance-api ...`
 
 ## format output
 - piping **xml** results to `xmllint` gives you nice formats. E.g. `curl -k --user marie:radioactivity "https://localhost:9200/ocs/v1.php/apps/files_sharing/api/v1/shares" | xmllint --format -`