- 1 Blueprint: Automated Performance Tests
- 1.1 Target Versions/Milestones
- 1.2 Goals / Motivation
- 1.3 Concept
- 1.4 Implementation Details
- 1.5 Risks
- 1.6 Issues and reviews
- 1.7 Dependencies upon other Blueprints
- 1.8 External links for clarification of technologies
Blueprint: Automated Performance Tests
|Proposal||Automated Performance Tests for TYPO3|
|Status||Draft, Discussion, Voting Phase, Accepted, Declined, Withdrawn|
|Current Progress||Unknown, Started, Good Progress, Bad Progress, Stalled, Review Needed|
|Topic for Gerrit||###gerrit_topic###|
- Started during TYPO3 CMS x.y development
Goals / Motivation
The goal is to monitor performance impact of changes merged to TYPO3 core. It's a must have for improving performance of the core.
After each commit to the core, Jenkings should perform tests, gather data and produce a report. Additionally it might send a warning if performance impact of the change is too big. It should be possible to see a trend (historical data) and a performance report for the current commit.
To implement fully automated performance test, the work needs to be done in the several areas. Performance tests scenarios might be implemented using JMeter.
- Dedicated machine is needed, for hosting tested TYPO3 instance. Hardware specification should be known.
- configuration needs to be updated, e.g. additional jobs for running performance tests
- Data provided by JMeter needs to be fetched
- It should be presented as graphs and numeric values
- Historical data should be available
- Most important scenarios for the Backend and the Frontend should be written down.
Performance tests implementation
- Testing scenarios should be implemented in e.g. using JMetter
- JMetter should be installed and configured
- Description of the testing environment (hardware, PHP settings, TYPO3 configuration, etc...)
- Documentation on how to run performance tests
- Tutorial how to write new tests and contribute
Issues and reviews
Dependencies upon other Blueprints
It might be worth investigating how performance tests are automated in the Magento 2: https://github.com/magento/magento2/tree/master/dev/tests/performance