2.3 deployment Flashcards
Development environment
developers check code on local machine using dummy data/sandbox
Test environment
used after development environment.
Staging environment
last testing environment before moving to production
Production environment
Live environment that end users see, should never be used for testing.
Also known as the AT/UAT
Acceptance Test, Universal Acceptance test are also known as the staging environment.
– Secure environment
– Writing code
– Developers test in their sandboxes
Development environment
– Application is live
– Rolled out to the user community
Production environment
– Still in the development stage
– All of the pieces are put together
– Functional tests
- large scale security analysis
Testing environment
– Verifies features are working as expected
– Validates new functionality
– Verifies old errors don’t reappear
Quality Assurance (QA)
– Almost ready to roll it out – Works and feels exactly like the production environment – Working with a copy of production data – Run performance tests – Test usability and features
Staging environment
– Helps protect against malicious users
– Attackers may not even be using your interface
Server-side validation
– All checks occur on the server
– Can filter legitimate input from genuine users
– May provide additional speed to the user
Client-side validation
– The end-user’s app makes the validation decisions
Code is constantly written and merged into the central repository many times a day. Has increase chance of vulnerability.
Continuous integration (CI)
Continuous delivery/deployment (CD) mean what?
• Continuous delivery
– Automate the testing process
– Automate the release process
– Click a button and deploy the application
• Continuous deployment
– Even more automation
– Automatically deploy to production
– No human integration or manual checks
