Skip to content

Commit

Permalink
Update preparation-for-going-live.md
Browse files Browse the repository at this point in the history
  • Loading branch information
andriitserkovnyi committed Feb 27, 2025
1 parent cbbc9d5 commit 25f664d
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/ca/dev/preparation-for-going-live.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ We've divided the preparation into approximate timeframes. Feel free to copy thi
| APP-28 | Application | Prepare DB creation in production | Prepare and implement database creation in production. For example, commit Propel migration for production and update the deploy file to install the database from the committed migration files. | |
| TES-04 | Testing | Test third-party integrations on production | - Collect instructions and requirements from the third-party providers for using services in production mode. <br>- Update integrations and plugins to use production credentials. <br>- Test all functionalities of the integrations and plugins to ensure they work as expected. <br>- Conduct load testing: Simulate real-world traffic on your application to assess its performance under load. This helps identify any bottlenecks that could cause performance issues during peak traffic times. | In some cases, you may need to comply with specific additional security measures, such as IP whitelisting or port configuration. | |
| TES-05 | Testing | Conduct load tests | Test how the platform performs under real-life circumstances. Define the performance acceptance criteria - the sample testing data should be comparable to the size and complexity of the production data. Monitor the application's performance metrics, such as response times or resource usage, during the tests. | Some options to define key metrics: <br>- Historical data: if you have existing traffic data–for example, from Google Analytics <br>- [Industry benchmarks](https://databox.com/website-traffic-benchmarks-by-industry): research typical traffic volumes for similar e-commerce sites in your industry <br>- Business goals: Consider target sales, conversion rates, and marketing campaigns to estimate expected traffic
| TES-06 | Testing | Conduct stress and performance tests | Test your production environment and assess its performance. Because production environments typically employ horizontal auto-scaling, it's essential to test under expected average and peak loads. These tests enable our team to optimize the environment's vertical scaling in advance, ensuring that it can seamlessly handle the expected loads from the get-go without any potential delays caused by auto-scaling mechanisms. This proactive approach eliminates the need for post-launch adjustments. Learn more [here](https://docs.spryker.com/docs/ca/dev/environment-scaling.html) | To make this process work effectively, maintain active communication with us. Inform us about your load and performance test plans and share the results so that we can fine-tune the environment to meet your requirements. | To make this process work effectively, maintain active communication with us. Inform us about your load and performance test plans and share the results so that we can fine-tune the environment to meet your requirements. |
| TES-06 | Testing | Conduct stress and performance tests | Test your production environment and assess its performance. Because production environments typically employ horizontal auto-scaling, it's essential to test under expected average and peak loads. These tests enable our team to optimize the environment's vertical scaling in advance, ensuring that it can seamlessly handle the expected loads from the get-go without any potential delays caused by auto-scaling mechanisms. This proactive approach eliminates the need for post-launch adjustments. For more information, see [Environment scaling](https://docs.spryker.com/docs/ca/dev/environment-scaling.html) | Maintain active communication with us. Inform us about your load and performance test plans and share the results so that we can fine-tune the environment to meet your requirements.
| TES-07 | Testing | Conduct penetration testing | We highly recommend having the project penetration-tested by an independent third-party provider and addressing the identified vulnerabilities. Before conducting a penetration test, inform us at least two weeks in advance by filling out [this form](https://docs.google.com/forms/d/e/1FAIpQLSfunn1HY-nsqueP6sRQSLmScUWlmmQyQJk9cscIVIP_5BmuOw/viewform?usp=sf_link).
| TES-08 | Testing | Import real data | After importing real data to production, double-check the completeness and accuracy of the migrated data, especially if transitioning from another platform. | Start working with data of realistic size and quality as early as possible. At this point, you must be importing data regularly to all your environments. We recommend working with the same import data across all environments. This significantly simplifies troubleshooting and helps you estimate import performance, leading up to your go-live and helping us with environment sizing considerations.
| TES-09 | Testing | Test checkout and OMS | Validate the checkout and OMS process: general checkout steps, shipment, payment, OMS. Test all checkout steps, including adding different items to the cart, entering shipping and billing information, selecting a payment method, and placing an order. Also, test the order fulfillment process to ensure that orders are processed and shipped correctly.
Expand Down

0 comments on commit 25f664d

Please sign in to comment.