So together they both make a nice full suite for testing and this simple example shows exactly that. And often you want to have something to run your e2e tests before or after your cloud deployment and that's exactly what KintoHub Jobs are for.
- Make sure you set 256mb minimum for this job to run -> required to start chrome *described in steps bellow
- Apply this template to your Github
- Connect your GithubApp to KintoHub.
- Create a JOB on KintoHub and select the Repository you just generated on your account.
- Set the name for your job
- Docker file is inclueded in the repo so you just press Create Job*
Then on your Master branch click
Build Latest Commit.
Once complete, Click Now click
Add To Project.
Build & Deployment Configurations
- Once added to a project -> open configuration side panel for your block by click a small gear icon on your block in dependencies list
- Set Memory Limit to 256 MB
- Press Done Configuring
And now you're ready to go live Click
Deploy and once done -> go to Logs to see your job running.
*make sure you select history logs to monitor your job (since real-time logs only crab logs while pod is running which in case of a jon being killed immediately after script's execution)
You can do a lot with KintoHub and your deployed application. Some helpful links for next steps that you may consider with this project.