Christian is an active developer of TYPO3 CMS. He handed in his first core patch back in July 2007. Today he’s involved in most of the main architectural core changes. In his work time, Christian is usually busy improving the TYPO3 core codebase.
Serious Software Testing: TYPO3 Runs Its 20,000th Build!
Consistent software testing is the key to a successful, long-term and high-quality solution. TYPO3 CMS has a well-established testing process. Every change that’s made to the core runs through the complete process before getting merged into the system. We’re proud to announce that the 20,000th build process since mid 2016 was run several days ago!
Read moreTesting TYPO3’s Core - Part VIII: Future
Software is never perfect. TYPO3 CMS is no exception and its development is always work in progress. Besides, zero bug state simply doesn’t exist. In short, there’s always room for improvement and also a lot of new ideas lined up. Join us for a glimpse into TYPO3’s future!
Testing TYPO3's Core - Part VII: A Historical View
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!
Testing TYPO3’s Core - Part VI: Integrity Tests
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.
Testing TYPO3’s Core - Part V: Acceptance Tests
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.
Testing TYPO3’s Core - Part IV: Functional Tests
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?”.
Testing TYPO3’s Core - Part III: Unit Tests
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.
Testing TYPO3’s Core - Part II: On Hardware & Dockers
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.
Testing TYPO3's Core - Part I: Infrastructure
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.
Atlassian Bamboo Apache Struts Security Post Mortem
On Monday (March 6th, 2017), information about a Zero-Day Vulnerability Remote Code Execution (CVE-2017-5638) in Apache Struts actively exploited in the wild was made public and pretty quickly spread through the well known web channels.