Thoroughly testing the functions of your solution helps to ensure a good user experience.
When testing the functionality of your project, consider the following:
A client did not spend enough time on testing to determine the right performance tier for their project size, implementation, and traffic. They had no issues initially, but the performance tier they used was discontinued and they were forced to change tiers.
Since they didn't have performance and load testing, they blindly chose an option they thought would work. However, during peak hours, the website went down because the selected performance tier was not able to handle the load.
The client immediately upgraded to a higher performance tier (via Azure management portal), but given the size of the database, the operation took some time and the website was offline for several hours.
A partner didn't collect use cases at the beginning of the project. As a result, they failed to include testing of use cases into their workflow before delivering the finished website.
One of the most important features was collecting visitor data for personalization and marketing automation in the later stages of the project. The partner did not configure forms to map submitted data to contacts. This meant the collected data wasn't available for Kentico's online marketing features.
This caused a serious delay in delivering the project to the customer and pushed the project over the planned budget. If they had identified these use cases up front, they would have been able to avoid the delay.
A client's website started displaying links to malicious websites. The first thought was that there was a severe security issue with the out-of-the-box software.
They were unable to confirm this, however. During the investigation, it was revealed that a solution partner implemented custom code that contained a SQL injection vulnerability. The vulnerability was introduced in a custom search filter which used where conditions to filter out the search results.
This where condition was not sanitized for malicious user input. Penetration testing could have identified this issue ahead of time, but the partner didn't include penetration tests into their project workflow.
Regression testing is an important step to ensure that previously tested parts of the software still perform correctly when adding new functionality.
When testing the implementation, you should:
When running performance, load, and capacity tests, there are several things you need to consider:
The next guide in this handbook will cover important considerations regarding how you deploy and host your project.