This repository has been archived by the owner on Nov 26, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've added the performance tests for CAPIF, using the original ones as base. These cover the correct usage of the API, not those that are expected to fail.
Everything is contained in a separate folder (
perf_tests
), and there is an additional script inservices
(runCapifPerfTests.sh
) that is equivalent to the original one.At the moment the tests are controlled by two variables defined in
perf_tests/resources/performance.resource
: The number of iterations and the threshold in seconds to consider that each separate try is successful. For quick testing I've left the iterations set to 2, but on the real trials this should be changed to something much higher (we used 100 on the first release).Let me know if something is not working as expected or needs to be changed, or if you have any question about this.