I’m busy re-writing my one day training course on Java For Testers, incorporating the lessons learned from finishing the Java For Testers book, and from running the training before.
A one day public training is being held in Amsterdam on 5th October.
I try to make my face to face training work for everyone - that means, people who are more advanced, and people who are absolute beginners.
Rather than just work through Java For Testers on a page by page basis, I’ve restructured the approach and code so that absolute beginners learn by filling in the blanks. i.e. I have code, then we comment out a line, fix the line or fill in the blanks. This helps absolute beginners avoid too may syntax errors and as the day progresses the exercises have more freedom.
Alongside all of that, I have to make sure that the more advanced people aren’t just uncommenting code. So I also have to create ‘bonus point’ style exercises that offer less hints, but allow the exploration of the topic and educates people with more experience.
What’s interesting (for me) is that his has led to a different order of presentation.
- running tests from command line
- IntelliJ Hints and Tips
- Primitives and Operators
- Primitive Wrapper Classes and static methods
- Logical Operators
- if, switch, ternary
- Create your own objects
- Arrays and Loops
- JUnit @Before, @After
- Random Data
- Create your own project
- Automation Libraries and More Advanced Topics
Create your own project and setup a pom.xml is one of the last things we cover on this course, which I think is slightly counter intuitive from a normal training course, but is pretty much exactly how most of us work in the real world since we spend a lot of time working with other people’s code. Reading it, tweaking it, amending it slightly. And then adding new classes into the code base.
This should mean that it is easier to take absolute beginners forward very quickly on a day training session.
This training is being run for the public in Amsterdam on the 5th October in conjunction with Xebia.