Technical Test: Difference between revisions
Jump to navigation
Jump to search
Created page with "==Technical Test== ====What is CI/CD?==== CICD is the combined practices of continuous integration and continuous delivery or continuous deployment. CI/CD bridges the gaps b..." |
|||
| Line 10: | Line 10: | ||
====Box Model==== | ====Box Model==== | ||
The CSS box model is essentially a box that wraps around every HTML element. It consists of: margins, borders, padding, and the actual content. | The CSS box model is essentially a box that wraps around every HTML element. It consists of: margins, borders, padding, and the actual content. | ||
====TDD/Unit Tests/FIRST==== | |||
FIRST properties of Unit Tests. | |||
* 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. | |||
Revision as of 00:12, 18 April 2022
Technical Test
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.
MEAN Stack
MEAN (MongoDB, Express.js, AngularJS (or Angular), and Node.js)
Box Model
The CSS box model is essentially a box that wraps around every HTML element. It consists of: margins, borders, padding, and the actual content.
TDD/Unit Tests/FIRST
FIRST properties of Unit Tests.
- 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.