// Add steps as necessary for accessing the software, post-configuration, and testing. Don’t include full usage instructions for your software, but add links to your product documentation for that information.
//Should any sections not be applicable, remove them

== Test the deployment

As shown in <<2-stacks-created>>, your deployment has created two AWS CloudFormation stacks: an Elastic Beanstalk stack with a randomly generated name and a CodePipeline stack that was named when you deployed the Quick Start. (The name of the CodePipeline stack also appears under the *Outputs* tab, as shown in <<cfn_outputs>>). 

:xrefstyle: short
[#2-stacks-created]
.Two stacks created during deployment
[link=images/2-stacks-created.png]
image::../images/2-stacks-created.png[Stacks,width=80%,height=80%]

Test the deployment as follows:

. Open the CodePipeline console, and view your https://console.aws.amazon.com/codesuite/codepipeline/pipelines[created pipelines^]. Verify that the status of the pipeline created in this deployment is *Succeeded*, as shown in <<pipeline-succeeded>>. 

[#pipeline-succeeded]
.Pipeline with "Succeeded" status
[link=images/pipeline-succeeded.png]
image::../images/pipeline-succeeded.png[Pipeline succeeded,width=80%,height=80%]

[start=2]
. Navigate to the *Outputs* tab for the Elastic Beanstalk CloudFormation stack, as shown in <<load-balancer-url>>. Choose the load-balancer URL, and verify that the webpage loads.

[#load-balancer-url]
.Load-balancer URL
[link=images/load-balancer-url.png]
image::../images/load-balancer-url.png[Load-balancer URL,width=80%,height=80%]

[start=3]
. Navigate to the Elastic Beanstalk environment created by AWS CloudFormation, choose the URL for the application, and confirm that your sample application is deployed from GitHub.
. Modify the sample application code of your forked GitHub repository, and check in the changes. 
. Verify that CodePipeline starts the CI/CD process and deploys your latest code changes to Elastic Beanstalk.