Among the wide range of options for professional TYPO3 hosting in the cloud is AWS Elastic Beanstalk; an easy-to-use service for deploying and scaling web applications. Learn more about this solution and how to deploy TYPO3 instances in this article.
The release of TYPO3 v10 is just around the corner! In this second part of his series on testing TYPO3, Peter Kraume explains how to report an issue with the use of Forge and Forger and how to pick and test patches.
It's just a few weeks until the new TYPO3 v10 will be released! This blog post illustrates how to set up the newest TYPO3 version and download and apply the latest patches.
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!
Due to the nature of code, software will never be entirely bug-free. However, a systematic review process ensures avoiding vulnerabilities and provides high-quality software. The code in a powerhouse CMS like TYPO3 is complex. If you’re running your site on an older version, keep it safe by opting for Extended Long Term Support (ELTS) and prolonging your website's lifespan.
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!
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!
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.
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.