So, you're almost ready to release an update but you want to make sure everything works End-to-End (E2E). You can install and maintain your own testing system that's separate from Frontastic but will work with your site. In this article, we'll show you how you can go about setting this up (but not a full step-by-step guide as it will depend on the Continuous Integration system you want to use).
Firstly, you'll need to reach out to us to get a test project. We'll provide you with a separate project from your existing one so it can be designated for testing. As a Developer, you'll have full control of the displayed data and as it's not a part of your 'real' project, Frontend Managers won't be able to accidentally change the test fixtures.
Then, you can set up your E2E testing infrastructure.
You can use any Continuous Integration system to do this, but you'll need some add-ons. For example, if you're using Jenkins CI or GitLab CI, you'll need to add Selenium or Browserstack.
Within your testing project in Frontastic, you could create all pages, routes, and all features that you could use in your project so as to test every possibility.
In the future, we'll provide you with a webhook capability so you can trigger your E2E tests after a successful deployment to the Staging environment. But in the meantime, you can start the deployment manually when you want to. See the deployment article for more information.
You can then execute your E2E testing infrastructure against these pages in your testing project and check the results.
Once your tests have run successfully, you're now ready to deploy to Production using the Frontastic studio, click Developer, then Deployment.
Updated almost 3 years ago