This is an extra feature we have build for automation purposes, but i would like you to show what we have done. We have defined 5 stepsLees meer
This is an extra feature we have build for automation purposes, but i would like you to show what we have done. We have defined 5 steps
This blog puts all the pieces together and create a continuous delivery pipeline
The smoketest is configured, so now we will be configuring the suitetest for complete testing of our application.
A few weeks ago, Developers.nl organised a technight about Chrome Dev Tools, presented by Prashant Palikhe. If you are a webdeveloper using Chrome, you are probably already aware of the existence of these tools; if not, you are really missing out on some awesome tools to make your work a lot easier. However, if you are like me, you're only using a small subset of the tools available; this talk presented some of the options I didn't know about yet.
After the integration is done we need to create a smoke-test. This is a simple test to see if everything is working before executing the suite-test
After configuration to release our artifact in nexus, we need to add integration-test to test the functionality of the software
For creating release artifacts and store them in Nexus, we need to create a release profile in our project.