![]() The changes we made to the Dockerfile and test.json have made the Concurrency, Ramp Up, Hold For, and HTTP endpoint under test fields useless, but they are still required in order to submit the form. Fill out the Name, Description, and Task Count fields with values you want for your test. Hit the Create Test button at the top of the page to navigate to the load testing setup. Go find that email, click on the console link, and sign in with the given credentials. Note: If you need to make multiple changes to the image, be sure to add ‘- no-cache’ to the end of the command on step 2.Īfter the commands finish running, we’re ready to run the tests!Īfter the stack finished deploying, you should have gotten an email with a username, password, and link to the load testing dashboard. Copy and paste the four commands given to you by AWS in order to update the image. On your local machine, open up a command prompt and navigate to the. There are four commands given to update the repository with our changes. Select the load testing repository in your list to bring up the list of images.įrom here, you want to click on the View push commands button in the upper right to get a set of commands specific to your repository. We can now go into the ECS service and navigate to the Amazon ECR Repositories link on the lefthand side of the page. Now we need to push our changes into ECS.īy now, the stack we deployed into AWS should have finished. Update Dockerfile to include the new JSON filesĪt this point, we are done editing the source. The script value on line 11 is going to be the name of your exported collection from Postman.ģ. ![]() You can change the value in iterations on line 5 to however many times you want your collection to run.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |