Editing Technical Test (section)

===general programming===
====What is CI/CD?====
CICD is the combined practices of continuous integration and continuous delivery or continuous deployment. CI/CD bridges the gaps between development and operation activities and teams by enforcing automation in building, testing and deployment of applications.

====TDD/Unit Tests/FIRST====
FIRST properties of Unit Tests. http://agileinaflash.blogspot.com/2009/02/red-green-refactor.html
* Fast: unit test must be fast - A software project will eventually have tens of thousands of unit tests, and team members need to run them all every minute or so without guilt. 
* Isolated: Tests isolate failures. A good unit test has a laser-tight focus on a single effect or decision. Good tests interferes with no other tests in any way. They impose their initial state without aid from other tests. They clean up after themselves.
* Repeatable:  Tests must be able to be run repeatedly without intervention.
* Self-validating: Tests are pass-fail.
* Timely: Tests are written at the right time, immediately before the code that makes the tests pass.

====TDD: Red/Green/Refactor====
http://agileinaflash.blogspot.com/2009/02/red-green-refactor.html
* Red: Failed test
* Green: Passed test
* Refactor: Clean up. Remove code. make into smaller units. performance.
====Types of Tests====
* Unit Tests - small. quick. Jest/NUnit/PHPUnit
* Integration Tests - connect components to see how they work together. Slower to write/run.
* Automation Tests - UI test/end-to-end tests. simulate user behavior.  Nightmare (https://github.com/segmentio/nightmare).

====AUTH====
=====JWT=====
=====OAuth=====