6. 1. TDD
Software development practice
First understand the requirement
Create test that tests this requirement
Run test and expect FAIL
Provide basic implementation
Run test and expect PASS
Improve your implementation to test
changes
8. 2. CI
Software development practice
Continuous commit (at least once, best
several times a day)
Run UT/IT tests (githooks) in local
environment before commit.
Continuous build and Deploy: check
Functional tests, performances, …
Why?
Each integration is verified by an automated
build (including test)
detect integration errors as quickly as
possible.
it helps the code stay robust enough
ensure that you are not committing buggy
code.
11. 3. CD
Next step of CI
Every commit, change to the system, can
be released for production at the push of a
button
Manual Release (RC)
Why?
Get automatic and fast feedback from
production like environment with each
commit.
Prepare for deployment Pipelines
13. 4. CDP
Conclusion of CD
Confused with CD
The release to production is completely
automated
Every validated commit is automatically
released to production
Why?
Create deployment Pipelines: Automated
implimentation of your application’s build,
deploy, test and release process.
17. 6. CI Android/Jenkins / Install
Download the appropriate package from: https://jenkins-ci.org/
If you use the .war package:
$ cd /Documents/jenkins Jenkins
$ java –jar jenkins.war
If you use the Jenkins-OSX installer package
- Follow the steps of the installer (License, destination, …)
- Restart the computer
Point your browser to: http://localhost:8080