The road to establishing the best possible workflow patterns for testing TYPO3 has been long and winding. It has been filled with up and downs and loads of lessons have been learnt along the way. Today the test environment runs efficiently. Join us for a glimpse behind the scenes!
Teaching can be a rewarding experience - both for you as a mentor and your student. Gestures and facial expressions speak for themselves. However, if you help someone online, all personal reaction gets lost. SkillDisplay shows you how to give credit to your learning resources and use SkillUp buttons.
Integrity tests are an integral part of TYPO3’s quality assurance process. This fourth and final step in our review process is used to check communication paths between different parts of the system and shows that all modules work correctly together. If all runs smoothly, a patch is then merged into the core.
Learning can be fun. SkillDisplay is a platform which offers pre-built learning paths, the so-called SkillPaths. It aims at making students more independent by offering precise guidelines and tracking acquired skills.
All non-trivial software has bugs, they're an inevitable byproduct of writing software. It's a systematic review process which keeps them to an absolute minimum and ensures a high-quality. Acceptance tests are the third step we use for testing TYPO3's core before merging patches into the system.
After making changes to TYPO3´s core we always run a series of testing which consists of four different steps. Functional tests are an integral part of this review process and give answers to the questions “Did we build a correctly working software?” and “Does the software meet the business requirements?”.
Units are the smallest testable parts of software. The workflow patterns we use for testing TYPO3´s core have evolved over time and unit testing became an integral part quite a few years ago. This was after experiencing rather strange issues when first integrating the scheduler into the core.
Developing a successful and strong software requires a decent development platform with specific hardware, third-party software and parallelization of jobs. An efficient communication between this setup and other parts of the system ensures that processes run smoothly and swiftly.
Automatic testing is integrated into the process of developing TYPO's core. Every patch version that is pushed to the review system goes through a standard process and multiple verification ensures that the software conforms to requirements.
With every powerful system comes a more or less steep learning curve, and these don’t go together with “quick wins” - leaving behind mixed results in terms of quality.