Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
java-samples
Main purpose
The idea is show my knowledge and an ability write Java code. Plus enhance coding skills.
How it works
I write a simple algorithm on Java by adding one realization. Definitely, before writing actual code, I prepare a unit test for it. Then I push the code as PR into the main repository. And after some time (approximately 2-4 minutes) checking results. I mean check Travis CI (Are there errors?), check Codacity (Does my PR up to coding standards?). If there are no errors I merge the PR into the master branch and those changes become a part of the main repository. If there are errors I make new commit into the PR to fix errors. Then I repeat a process from step 4 (sentence 4 of this paragraph) until changes will be merged with the master branch.
Table of content
- Primitive types class
- Counter class, demo, 6 unit tests
- FindMax class, demo, 6 unit tests
- FindMin class, demo, 4 unit tests
- FindSecondMax class, demo, 4 unit tests
- ReverseArray class, demo, 2 unit tests
- IsPalindrome class, demo, 5 unit tests
- Fibonacci class (recursion), demo, 3 unit tests - (not optimal for big integer numbers and slow)
- FibonacciMemo class (recursion & memoization), demo, 3 unit tests - (optimal for huge integer numbers and fast!)
- Page class, DuckDuckGoPage class, DuckDuckGoResultPage class, one functional UI test - (JUnit, Selenium, Firefox)
- Conditions class, demo, 5 unit tests
- Coin class, demo, 1 unit test
- Dice class, demo, 1 unit test