Ensuring that your app works across all the devices, operating systems, and browsers that your users can access it is a daunting task. Market share figures from Net Applications will tell you that Internet Explorer still reigns supreme, while StatCounter will tell you that Chrome won the browser war globally a long time ago. The sure shot way to ensure that your end-user experience is sound is by testing across the major platforms used by your users to access your app. Fortunately, our friends at Sauce Labs offers an industry-leading platform in solving this problem, and automating the Sauce Labs workflow in Solano CI is easy and secure.
Sauce Labs – What do they do?
Test Securely via Sauce Connect
Sauce Connect is a secure tunneling app which allows you to execute tests securely when testing behind firewalls via a secure connection between Sauce Labs’ client cloud and Solano CI. Sauce Connect allows you to test staged apps behind a firewall while maintaining control of proxy and policies. To use Sauce Connect in Solano CI, there are only two things you need to do:
- Set the
SAUCE_ACCESS_KEYenvironment variables for your builds. The
solano config:addcommand should be used to set sensitive environment variables.
- Ensure you have the latest version of Sauce Connect installed and start it as a background process for your workers. This can be done by merging the following setup hooks in your solano.yml configuration file. Our karma-sauce-example repository is a working demonstration of using Sauce Connect in this manner.
tar -xzf sc-latest-linux.tar.gz
(cd sc-*-linux && ./bin/sc -u $SAUCE_USERNAME -k $SAUCE_ACCESS_KEY) &
One Step Closer to Continuous Delivery
Now that you have successfully setup your continuous integration workflow to test your changes across all the things, the next step toward a continuous delivery workflow would be to automate your deployment. Solano CI offers a multitude of options for deployment, from running your deploy script to deep integrations with cloud infrastructure partners like Amazon Web Services, Heroku, and Engine Yard. Check out our docs on Deployment and Post-Build for more info. As always, ping us at firstname.lastname@example.org if you have any questions or comments!