Agenda
- Why are we doing it?
- What happened since 2010?
- What are the next steps?
- Q&A / Your ideas
- Hands on / Workshop
TYPO3 CI
New Ideas
Status Report + Workshop
Why are we doing it?
Disclaimer
I'm not a marketing guy but…
… but what I learned fro other projects at dkd EVERY project improves when thinking about QA Doing the right things and more right things will follow.
It's not only cool nor enough to run automated task and have shiny dashboard. .notes The whole idea behind CI and Metrics gets easier to gasp if we think of our users and developers as customers. .notes Although it's open source we have to think out of the box. .notes Other systems already shine and have more transparency. We should catch up as quick as possible.
We should care more about our customers
– Sincerly Christian
Thread users as customers
Thread developers as customers
Customers ❤ Transparency
Customers ❤ Processes
Customers ❤ Quality
Devs ❤ Transparency
Devs ❤ Clean Code
Devs ❤ Stability
How do we prove the world, we have a stable release candidate?
Do we have a stable
release candidate?
How do we prove the world, we have a stable product?
.notes Do you want to ship a product
that is not tested? (testing by hand equals "not tested")
Is TYPO3 a stable product?
untested is considered unstable
TYPO3 needs more QA
dkd is dedicated to bring QA to TYPO3 .notes It's crucial for companies to have a stable product
We - as a community and as (Core) Devs - are responsible for TYPO3's success. It touches every developers feelings. I don't want to tell you this. But I feel the urge to.
How much QA
do we already have?
Checks like Code Sniffer, PMD
commit > check > +1 / -1
for TYPO3 v4 Core master
Example check
# Check Coding Style
phpcs --extensions=php,inc --report=checkstyle
--report-file=build/logs/checkstyle.xml .
TER-Upload > metrics.typo3.org
for TYPO3 Extensions
Example metrics
% of comments
CGL Violations
Job Overview
https://ci.typo3.org/view/TYPO3/view/Core/
Collect code metrics
- Find Hotspots in Code
- Developers can improve code
- We can only improve things we see
Next steps
Provide Infrastructure for all Tests
Unit, Integration, User Acceptance Tests
Unit- and Integration-Tests
on each commit
User Acceptance Tests
nightly
Cross-Browser Tests
before release
Build up a virtual environment
for each test run
Easy to reset with snapshots
TravisCI solves this already
http://travis-ci.org
Would love to test the service for TYPO3 - But Travis supports only GitHub-Projects at the moment
Challenge
TYPO3 is hard to test
requires decent amount of infrastructure
– please prove me wrong!
If it's hard to test it's probably bad code?! .notes History, Bad architecture, Depends on many things … We all know that … and things are getting better.
Different PHP-Versions, Servers, Databases, Cache backends
Who of you has set up Redis as Caching Backend? .notes Who has a full application stack to test TYPO3 with?
TYPO3 Dev machine?
Hard stuff!
Easy setup = more testing
At dkd we have very good experiences with production like environments.
Next steps 2
TYPO3 Test Environment As Code
Make TYPO3 infrastructure a community project as well
Use Chef to configure the machines
Collect best practices in one public repository
Provide Vagrant Boxes for
TYPO3-Community
Developers can easily setup a dev machine and start testing
Works very well at dkd
Cross-Browser Tests
with Selenium and SauceLabs
– Who want's to install IEs?
We can test the test-service to gain experiences .notes Showcase?
Showcase
Saucelabs sponsores several free minutes
Questions?
Thanks!
Workshop
Goals
Bestandsaufnahme
- Collect existing build scripts
- Collect ideas
- Get things real
Add your ideas here ☟
Hello Phoenix!
FLOW3 & Phoenix has it's own build server
That's OK but can we share experiences?
That would be awesome!
Many possibilities to improve TYPO3
without being a Core Dev ;)
I'm not a Core Dev as well. I'm a real bad coder. ;)
CodeSniffer
Collect more standards as Sniffs
Improve existing Sniffs
Setup repository