+ - 0:00:00
Notes for current slide
Notes for next slide

Day 1

Git, Gitlab, Intellij, Unit Testing

1 / 27

Gitlab

  • Is an open source git repository manager
2 / 27

Gitlab

  • Is an open source git repository manager
  • You can install it yourself and have your own "gitlab", see this
2 / 27

Gitlab

  • Is an open source git repository manager
  • You can install it yourself and have your own "gitlab", see this
  • Or you can use gitlab.com in a similar way you would use github.com
2 / 27

Gitlab

  • Is an open source git repository manager
  • You can install it yourself and have your own "gitlab", see this
  • Or you can use gitlab.com in a similar way you would use github.com
2 / 27

Gitlab compared to Github

3 / 27

Gitlab compared to Github

  • Gitlab is open source and you can setup your own internal gitlab
3 / 27

Gitlab compared to Github

  • Gitlab is open source and you can setup your own internal gitlab
  • Pull Requests are called Merge Requests
3 / 27

Gitlab compared to Github

  • Gitlab is open source and you can setup your own internal gitlab
  • Pull Requests are called Merge Requests
  • Free accounts can have private repos (Gitlab.com compared to Github.com)
3 / 27

Gitlab compared to Github

  • Gitlab is open source and you can setup your own internal gitlab
  • Pull Requests are called Merge Requests
  • Free accounts can have private repos (Gitlab.com compared to Github.com)
  • There are a few other minor differences, but nothing that should cause you any confusion
  • For a detailed list of differences see https://about.gitlab.com/comparison/
3 / 27

Gitlab user roles

  • You can add users to projects and groups with a certain role
  • Owner, Master - Can do pretty much anything
  • Developer - Can clone, pull, push, comment, approve merge requests
  • Reporter - Can clone and comment
4 / 27

Gitlab Setup

  1. Go to gitlab.com in your web browser
  2. Create an account (create new one or create using Github account)
  3. Create an SSH key by following these instructions (DON'T enter a pass phrase when prompted. Hit enter.)
  4. Send your gitlab username to the instructor so you can be added to certain groups
  5. Browse around the gitlab.com: groups, projects, settings...
  6. Clone a repo to make sure everything is setup correctly
5 / 27

How Will We Use Git

  • Via terminal, without the aid of a GUI
  • Why you ask?
6 / 27

How Will We Use Git

  • Via terminal, without the aid of a GUI
  • Why you ask?
  • Because it helps the git process to really sink in
6 / 27

How Will We Use Git

  • Via terminal, without the aid of a GUI
  • Why you ask?
  • Because it helps the git process to really sink in
  • Also we will create feature branches for our work
  • These will help keep our code organized
6 / 27

How Will We Use Git

  • Via terminal, without the aid of a GUI
  • Why you ask?
  • Because it helps the git process to really sink in
  • Also we will create feature branches for our work
  • These will help keep our code organized
  • When to create a new branch?
    • New assignment
    • Trying something out (experiment)
6 / 27

Git command review

7 / 27

Git command review

  • fork a repo - not an actual git command for this, but very useful
7 / 27

Git command review

  • fork a repo - not an actual git command for this, but very useful
  • git clone https://repo-url
7 / 27

Git command review

  • fork a repo - not an actual git command for this, but very useful
  • git clone https://repo-url
  • git status
7 / 27

Git command review

  • fork a repo - not an actual git command for this, but very useful
  • git clone https://repo-url
  • git status
  • git checkout branch-name
7 / 27

Git command review

  • fork a repo - not an actual git command for this, but very useful
  • git clone https://repo-url
  • git status
  • git checkout branch-name
  • git add * or git add . or git add specific-filename.txt
7 / 27

Git command review

  • fork a repo - not an actual git command for this, but very useful
  • git clone https://repo-url
  • git status
  • git checkout branch-name
  • git add * or git add . or git add specific-filename.txt
  • git commit -m "a most accurate message"
7 / 27

More Git Commands

  • git push
8 / 27

More Git Commands

  • git push
  • git pull
8 / 27

More Git Commands

  • git push
  • git pull
  • git fetch
8 / 27

More Git Commands

  • git push
  • git pull
  • git fetch
  • git branch and git branch -a
8 / 27

More Git Commands

  • git push
  • git pull
  • git fetch
  • git branch and git branch -a* gite remote
8 / 27

More Git Commands

  • git push
  • git pull
  • git fetch
  • git branch and git branch -a* gite remote
  • git remote show origin
8 / 27

More Git Commands

  • git push
  • git pull
  • git fetch
  • git branch and git branch -a* gite remote
  • git remote show origin
  • git remote add upstream url-of-a-repo
8 / 27

Git walkthrough

9 / 27

Intellij Refresher

10 / 27

Intellij Refresher

  • We will use Intellij Community Edition (It's free!)
10 / 27

Intellij Refresher

  • We will use Intellij Community Edition (It's free!)
  • We will also use JDK 8
10 / 27

Intellij Refresher

  • We will use Intellij Community Edition (It's free!)
  • We will also use JDK 8
  • Create a new project
  • Check JDK version in Intellij
  • Mark folders as src, test, lib, excluded...
  • Run your code
  • Run your tests
  • How to save files (they save automatically unless you turn that off)
10 / 27

Intellij Tips

11 / 27

Intellij Tips

  • Ctrl Enter - Generate menu
11 / 27

Intellij Tips

  • Ctrl Enter - Generate menu
  • Command shift o - Search for file
11 / 27

Intellij Tips

  • Ctrl Enter - Generate menu
  • Command shift o - Search for file
  • Command e - recently opened files
11 / 27

Intellij Tips

  • Ctrl Enter - Generate menu
  • Command shift o - Search for file
  • Command e - recently opened files
  • Command j - shows you a shorcut menu
11 / 27

Intellij Tips

  • Ctrl Enter - Generate menu
  • Command shift o - Search for file
  • Command e - recently opened files
  • Command j - shows you a shorcut menu
  • Command shift - and + - expands for collapses code folding
11 / 27

Intellij Tips

  • Ctrl Enter - Generate menu
  • Command shift o - Search for file
  • Command e - recently opened files
  • Command j - shows you a shorcut menu
  • Command shift - and + - expands for collapses code folding
  • Command / - adds // comment in front of selected lines (removes if already present)
11 / 27

Intellij Tips

  • Ctrl Enter - Generate menu
  • Command shift o - Search for file
  • Command e - recently opened files
  • Command j - shows you a shorcut menu
  • Command shift - and + - expands for collapses code folding
  • Command / - adds // comment in front of selected lines (removes if already present)
  • Alt + Enter - Intentions menu (offers to solve problems for you)
11 / 27

Intellij Tips

  • Ctrl Enter - Generate menu
  • Command shift o - Search for file
  • Command e - recently opened files
  • Command j - shows you a shorcut menu
  • Command shift - and + - expands for collapses code folding
  • Command / - adds // comment in front of selected lines (removes if already present)
  • Alt + Enter - Intentions menu (offers to solve problems for you)
11 / 27

Intellij Tips pt2

12 / 27

Intellij Tips pt2

  • Open multiple files by splitting vertically or horizontally
12 / 27

Intellij Tips pt2

  • Open multiple files by splitting vertically or horizontally
  • Middle click or CMD click to go to source of a class or method
12 / 27

Intellij Tips pt2

  • Open multiple files by splitting vertically or horizontally
  • Middle click or CMD click to go to source of a class or method
  • Show/hide method parameter name hints
12 / 27

Intellij Tips pt2

  • Open multiple files by splitting vertically or horizontally
  • Middle click or CMD click to go to source of a class or method
  • Show/hide method parameter name hints
  • Local history for a file - log of changes Intellij keeps (right click a file)
12 / 27

Intellij Tips pt2

  • Open multiple files by splitting vertically or horizontally
  • Middle click or CMD click to go to source of a class or method
  • Show/hide method parameter name hints
  • Local history for a file - log of changes Intellij keeps (right click a file)
  • Do you have any tips you want to share?
12 / 27

Java Project Structure Conventions

13 / 27

Java Project Structure Conventions

  • lib - contains jar files
  • out/build - the compiled class files
  • src
    • main - java sources files
    • test - test java source files
13 / 27

Refactoring

14 / 27

Refactoring

  • Changing code without changing its external behavior
  • When do you want to do this?
14 / 27

Refactoring

  • Changing code without changing its external behavior
  • When do you want to do this?
  • Better techniques come along
14 / 27

Refactoring

  • Changing code without changing its external behavior
  • When do you want to do this?
  • Better techniques come along
  • New requirements must be met
14 / 27

Refactoring

  • Changing code without changing its external behavior
  • When do you want to do this?
  • Better techniques come along
  • New requirements must be met
  • The presence of "code smells"
    • Duplication
    • Bad naming conventions
14 / 27

Examples of Refactoring

15 / 27

Examples of Refactoring

  • Renaming classes or methods
15 / 27

Examples of Refactoring

  • Renaming classes or methods
  • Moving methods to a different class
15 / 27

Examples of Refactoring

  • Renaming classes or methods
  • Moving methods to a different class
  • Moving classes to a different package
15 / 27

Examples of Refactoring

  • Renaming classes or methods
  • Moving methods to a different class
  • Moving classes to a different package
  • Using a new sorting algorithm
15 / 27

Examples of Refactoring

  • Renaming classes or methods
  • Moving methods to a different class
  • Moving classes to a different package
  • Using a new sorting algorithm
  • Using a feature in the language, that the previous coder didn’t know about
15 / 27

Examples of Refactoring

  • Renaming classes or methods
  • Moving methods to a different class
  • Moving classes to a different package
  • Using a new sorting algorithm
  • Using a feature in the language, that the previous coder didn’t know about
  • Validation rules need to change based on new requirements
15 / 27

After a Refactor

  • How do we know everything still work?
16 / 27

After a Refactor

  • How do we know everything still work?
  • We can give it the ol eye ball test... Looks good to me. Ship it!
16 / 27

After a Refactor

  • How do we know everything still work?
  • We can give it the ol eye ball test... Looks good to me. Ship it!
  • Manually test the application a few times... I don't see any bugs. Ship it!
16 / 27

After a Refactor

  • How do we know everything still work?
  • We can give it the ol eye ball test... Looks good to me. Ship it!
  • Manually test the application a few times... I don't see any bugs. Ship it!
  • Run the automated tests!... uh oh that thing I forgot about is broken :(
16 / 27

17 / 27

Automated Testing

18 / 27

Automated Testing

Automated tests are code files that utilize all the features of your code

18 / 27

Automated Testing

Automated tests are code files that utilize all the features of your code

  • Your classes are instantiated
18 / 27

Automated Testing

Automated tests are code files that utilize all the features of your code

  • Your classes are instantiated
  • Certain methods are executed (hopefully most of them)
18 / 27

Automated Testing

Automated tests are code files that utilize all the features of your code

  • Your classes are instantiated
  • Certain methods are executed (hopefully most of them)
  • All in specific order to insure they all do what they are supposed to
18 / 27

Benefits of Automated Tests

19 / 27

Benefits of Automated Tests

  • They verify that the code functions as it should
    • All good here
    • Oops, I just broke something with that last change
19 / 27

Benefits of Automated Tests

  • They verify that the code functions as it should
    • All good here
    • Oops, I just broke something with that last change
  • The tests themselves are documentation on what the code should do
    • Because the tests demonstrate proper usages of the code
    • With all the required inputs and expected outputs
19 / 27

Benefits of Automated Tests

  • They verify that the code functions as it should
    • All good here
    • Oops, I just broke something with that last change
  • The tests themselves are documentation on what the code should do
    • Because the tests demonstrate proper usages of the code
    • With all the required inputs and expected outputs
  • Unlike in code comments the tests can’t become stale
    • Tests will fail if the code behavior changes
19 / 27

Unit Test

A specific type of automated test.

20 / 27

Unit Test

A specific type of automated test. What is a “unit”?

20 / 27

Unit Test

A specific type of automated test. What is a “unit”?

  • The smallest testable unit of work
    • Most likely that is a function, but not always
20 / 27

Unit Test

A specific type of automated test. What is a “unit”?

  • The smallest testable unit of work
    • Most likely that is a function, but not always
  • A single, clearly stated, desired behavior
    • Breaking it down this way makes is easier to find bugs when issues arise
20 / 27

Unit of Work Examples

A single, clearly stated, desired behavior

21 / 27

Unit of Work Examples

A single, clearly stated, desired behavior

  • Method returns false if passed an empty array
21 / 27

Unit of Work Examples

A single, clearly stated, desired behavior

  • Method returns false if passed an empty array
  • Method throws exception if passed a negative number
21 / 27

Unit of Work Examples

A single, clearly stated, desired behavior

  • Method returns false if passed an empty array
  • Method throws exception if passed a negative number
  • Class constructor properly creates object when passed required parameters
21 / 27

Best Practices

22 / 27

Best Practices

  • Test should be deterministic
22 / 27

Best Practices

  • Test should be deterministic
    • Given the same starting state, the test will always have the same result
    • A test that passes “most of the time” is not a good test.
22 / 27

Best Practices

  • Test should be deterministic
    • Given the same starting state, the test will always have the same result
    • A test that passes “most of the time” is not a good test.
  • Grouped together properly and focused
    • Don’t test totally unrelated things in the same test method or even the same test file
22 / 27

Best Practices

  • Test should be deterministic
    • Given the same starting state, the test will always have the same result
    • A test that passes “most of the time” is not a good test.
  • Grouped together properly and focused
    • Don’t test totally unrelated things in the same test method or even the same test file
  • Tests should pass before committing code
22 / 27

Best Practices

  • Test should be deterministic
    • Given the same starting state, the test will always have the same result
    • A test that passes “most of the time” is not a good test.
  • Grouped together properly and focused
    • Don’t test totally unrelated things in the same test method or even the same test file
  • Tests should pass before committing code
  • Don’t test getters and setters
22 / 27

Writing a Unit Test

23 / 27

Writing a Unit Test

The AAA's method helps to guide us

23 / 27

Writing a Unit Test

The AAA's method helps to guide us

  • Arrange
    • Variables that you will need
23 / 27

Writing a Unit Test

The AAA's method helps to guide us

  • Arrange
    • Variables that you will need
  • Act
    • Call method(s)
23 / 27

Writing a Unit Test

The AAA's method helps to guide us

  • Arrange
    • Variables that you will need
  • Act
    • Call method(s)
  • Assert
    • Check for specific results
23 / 27

Unit Test Components

24 / 27

Unit Test Components

  • Test
    • A single test function
24 / 27

Unit Test Components

  • Test
    • A single test function
  • Fixture
    • A class file containing one or more test functions
24 / 27

Unit Test Components

  • Test
    • A single test function
  • Fixture
    • A class file containing one or more test functions
  • Test Runner
    • A library that executes the tests and provides a report
    • For us this will be a library called JUnit
24 / 27

JUnit

A Java library that provides classes, methods, and assertions for organizaing and executing unit tests.

25 / 27

JUnit

A Java library that provides classes, methods, and assertions for organizaing and executing unit tests.

  • Specifcally JUnit 4
25 / 27

JUnit

A Java library that provides classes, methods, and assertions for organizaing and executing unit tests.

  • Specifcally JUnit 4
  • Why not JUnit 5? For some reason the Java testing community has not widely adopted it yet
25 / 27

JUnit Annotations

26 / 27

JUnit Annotations

  • @Fixture
26 / 27

JUnit Annotations

  • @Fixture
  • @Test
26 / 27

JUnit Annotations

  • @Fixture
  • @Test
  • @Before
26 / 27

JUnit Annotations

  • @Fixture
  • @Test
  • @Before
  • @After
26 / 27

JUnit Annotations

  • @Fixture
  • @Test
  • @Before
  • @After
  • @BeforeClass
26 / 27

JUnit Annotations

  • @Fixture
  • @Test
  • @Before
  • @After
  • @BeforeClass
  • @AfterClass
26 / 27

Instructor Led Walkthrough

27 / 27

Gitlab

  • Is an open source git repository manager
2 / 27
Paused

Help

Keyboard shortcuts

↑, ←, Pg Up, k Go to previous slide
↓, →, Pg Dn, Space, j Go to next slide
Home Go to first slide
End Go to last slide
b / m / f Toggle blackout / mirrored / fullscreen mode
c Clone slideshow
p Toggle presenter mode
t Restart the presentation timer
?, h Toggle this help
Esc Back to slideshow