Commit 2f45f1f1 authored by Gerson Sunyé's avatar Gerson Sunyé

Maven presentation is now more general, about 'build automation'

parent f0e0169f
Pipeline #14785 passed with stages
in 4 minutes and 10 seconds
This diff is collapsed.
......@@ -32,13 +32,14 @@ Icons made by http://www.freepik.com[Freepik] from http://www.flaticon.com[Flati
* link:construction.html[Software Construction]
* link:mapping.html[Mapping Designs to Code - Part I]
* link:behavior.html[Mapping Designs to Code - Part II]
* link:evolution.html[Software Evolution]
* link:build.html[Automated Build]
* link:refactorings.html[Refactorings]
* link:evolution.html[Software Evolution]
* link:unit-test.html[Unit Testing]
* link:tdd.html[Test Driven Development]
* link:patterns.html[Design Patterns]
* link:ci.html[Continuous Integration]
* link:build.html[Build Configuration]
== References
......
......@@ -12,8 +12,18 @@
:includedir: includes
:sectids!:
= Unit Testing
////
TODO
https://www.petrikainulainen.net/programming/testing/writing-clean-tests-naming-matters/
https://enterprisecraftsmanship.com/posts/you-naming-tests-wrong/
////
= Test Automation
////
In software testing, test automation is the use of software separate from the software being tested to control the execution of tests and the comparison of actual outcomes with predicted outcomes.[1] Test automation can automate some repetitive but necessary tasks in a formalized testing process already in place, or perform additional testing that would be difficult to do manually. Test automation is critical for continuous delivery and continuous testing.
////
== Golden rule
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment