The content of the seminar sessions

The purpose of the seminars is to provide hands-on experience with the topics discussed in the lectures. The seminar content will cover various areas of code refactoring, testing, and static code analysis. The students will analyse and optimize multiple software quality attributes, such as reliability, maintainability, testability or performance with the help of modern open-source tools. The students will work in pairs on exercises during the seminars and on larger assignments (projects) at home. The attendance on the seminars is mandatory. Although, the seminars focus on the Java programming language, the principles discussed in the seminars are generally applicable also in other languages and environments.

Requirements

The maximum number of points to be obtained in the course is 100 and the required minimum for passing is 70. The distribution of the points is as follows:

• Active participation in lectures: 10 points
• Achievements in seminars (completing bonus tasks, nice solutions, extra activity etc.): 10 points
• Projects: 45 points
  • Assignment 1 (Refactoring): 15 points
  • Assignment 2 (Testing): 15 points
  • Assignment 3 (Performance testing, Static Code Analysis): 15 points
  • Special evaluation assignment
• Final colloquium assessment: 35 points

An additional requirement for passing the course is the completion of all assignments from the seminars.

Penalties

• Every second (and afterward) unexcused absence (note that one is allowed, and the first seminar session does not count):
  • -7 points.
• Late submission of project or assignment:
  • -3 points for each team member per day overdue.

Time Schedule:

• 18.2. [java1+java2] Introduction - maven, git, branching
• 25.2. [java2] Clean code, SOLID
• 3.3.   [java1] Clean code, SOLID
• 10.3. [java2] Code smells, refactoring
• 17.3. [java1] Code smells, refactoring
• 24.3. [java2] JUnit extensions, data-driven testing, Mockito, TDD   
• 31.3. [java1] JUnit extensions, data-driven testing, Mockito, TDD      
• 7.4.   [java2] Test plan, risk analysis, web app testing, Selenium, Issue processing,  
• 14.4. [java1] Test plan, risk analysis, web app testing, Selenium, Issue processing,
• 21.4. [java2]  Profiling, performance testing, Perfcake
• 28.4. [java1]  Profiling, performance testing, Perfcake
• 5.5.   [java2] Static Code Analysis,  Checkstyle, Continuous integration, code review
• 12.5. [java1]  Static Code Analysis Checkstyle, Continuous integration, code review

Projects

• There will be three larger assignments (separate mini-projects)
• First will focus on code refactoring, second on unit testing and third on the performance testing and static code analysis
• The deadline for each assignment will be 2-3 weeks
• Students will work in pairs
• Each project will have a set of optional (and more challenging) tasks, whose completion will be awarded by bonus points
• Additionally, there will be two special coding tasks. The first one will be introduced at the first seminar. Its purpose will be to evaluate students' current ability to write good quality code. The second one will be assigned at the last seminar. Its goal will be to evaluate the improvement of students' coding skills as a result of the course enrollment.

Basic study sources

Books

• Clean Code: A Handbook of Agile Software Craftsmanship
  • Robert C. Martin
  • Link
• Clean Architecture: A Craftsman's Guide to Software Structure and Design
  
  • Robert C. Martin
  • Link
• Refactoring to Patterns
  • Joshua Kerievsky
  • Link
• Refactoring: Improving the Design of Existing Code
  • Martin Fowler
  • Link
• xUnit Test Patterns: Refactoring Test Code
  • Gerard Meszaros
  • Link

Web

• http://sourcemaking.com/

Tutorials

• Maven:
  Maven.pdf
• Git: 
  gitBasics.pdf

Initial evaluation assignment

Clean Code

• Dirty/clean examples
  • https://github.com/twogood/how-to-clean-your-dirty-code/blob/master/src/main/java/se/softhouse/

SOLID

• Slides
• Download projects
• sample solutions to exercises will be later uploaded to the repository (packages problems and solution)
• at least for the LSP exercise, use the virtualbox image
• SOLID-tasks.docx

Bomberman exercise

• /auth/el/fi/jaro2020/PV260/um/seminars/java_groups/seminar_2/bomberman.zip
• find out how the game works
• look for examples of clean code/SOLID violations

Initial evaluation assignment survey

• https://forms.gle/uXsTNYQytwEZGoG89

Hangouts links

• Lasaris1: https://hangouts.google.com/group/S7gjpQMU9FGza1Xx7
  
• Lasaris2: https://hangouts.google.com/group/HaGAjacUoCuPigGS7
  

Refactoring

Demo example - RegEx Fractal

• clone the repository from: https://github.com/stanozm/PV260-refactoring-regexFractal
• refactoring.pdf
• notes-summary.docx

Refactoring exercise

• Download the exercise project from study materials
• It contains three exercises, each in separate package
• For each exercise, refactor the source code. Start with EquationSolver, if there is enough time, continue with Floodfill
• To find out, what the projects do, look at the tests (EquationSolver/Floodfill projects).
• Do not modify the tests during the refactoring 

Assignment 1: Code Refactoring

Further Reading

• https://sourcemaking.com/refactoring

Google Meet

• https://meet.google.com/mcx-ddiv-mdp

Video recording of the session

Testing

• slides
• Seminar4-Testing.mp4

JUnit Extensions

• for examples and exercies, clone the repository: https://github.com/stanozm/PV260-UnitTesting.git
• AssertJ: http://joel-costigliola.github.io/assertj/
• Catch-exception: https://github.com/Codearte/catch-exception
• Zohhak: https://code.google.com/p/zohhak/
• Junit-quickcheck: http://pholser.github.io/junit-quickcheck/site/0.7/

Mockito

• http://site.mockito.org/
• javadoc: http://static.javadoc.io/org.mockito/mockito-core/2.7.19/org/mockito/Mockito.htm
• download/clone the RomanCalculator demo from: https://github.com/stanozm/PV260-RomanCalc.git
• Exercise 
  • clone repository from: https://github.com/stanozm/PV260-Testing-CustomerAnalysis
  • Chyba: Odkazovaný objekt neexistuje nebo nemáte právo jej číst.

    https://is.muni.cz/el/fi/jaro2020/PV260/um/seminars/java_groups/seminar_4/CustomerAnalysisTest-solution.java

Test Driven Development

We will work with Socrative because of remote style of teaching. Please go there, fill the provided classroom name and wait for the instructions given by the lecturer. If you will be accidentaly signed out during the seminar, no problem. Just go there again and fill the same nickname as previous time. It will allows you to continue in the work. 

Archive

Record of the seminar (14. 4. 2020)

Socrative answers from exercises (both groups)

Materials

1/3 Test Plans

2/3 Issue tracking

3/3 Selenium (IDE + WebDriver)

Assignment 2: Testing

Obsah není zveřejněný.

Archive

Socrative answers from exercises (both groups)

Checkstyle

• slides 
• web - http://checkstyle.sourceforge.net/
• checks github - https://github.com/checkstyle/checkstyle/tree/master/src/main/java/com/puppycrawl/tools/checkstyle/check

Code review, Continuous integration

We will work with Socrative because of remote style of teaching. Please go there, fill the provided classroom name and wait for the instructions given by the lecturer. If you will be accidentaly signed out during the seminar, no problem. Just go there again and fill the same nickname as previous time. It will allows you to continue in the work. 

PV260-Seminar-7.pdf

Assignment 3

• https://is.muni.cz/auth/el/fi/jaro2020/PV260/um/seminars/java_groups/63275978/PV260___Assignment3.pdf
  

Final Evaluation Assignment

• https://is.muni.cz/auth/el/fi/jaro2020/PV260/um/seminars/java_groups/final_assignment/assignment.pdf