xpepper

// inside a step in the Jenkinsfile...
...
 jacoco(
     classPattern: '**/classes/kotlin/main',
     sourcePattern: '**/src/main/kotlin',
     sourceInclusionPattern: '**/*.kt'
 )
...

xpepper

post {
    always {
        archiveArtifacts artifacts: '**/build/libs/*.war', onlyIfSuccessful: true
        jacoco(
            classPattern: '**/classes/kotlin/main',
            sourcePattern: '**/src/main/kotlin',
            sourceInclusionPattern: '**/*.kt'
        )
    }
    success {

xpepper

build/
    classes
          kotlin
    jacoco
          test.exec
    reports
          jacoco

xpepper

build/
    classes
          kotlin
    jacoco
          test.exec
    ...          

xpepper

plugins {
    ...
    id 'jacoco'
}

xpepper

Add code coverage to a gradle project

In order to have code coverage measurement enabled on your gradle project, you have to just add the jacoco plugin to the build.gradle plugin section

plugins {
    ...
    id 'jacoco'
}

xpepper

(https://www.quora.com/Whats-the-difference-between-a-Junior-Intermediate-Senior-developer)

What's the difference between a Junior / Intermediate / Senior developer?

Junior is capable but needs someone with more experience to teach, mentor, guide, or direct them. They are still learning, on the job, and you should expects the risks associated with such a person.

Intermediate can work on their own but isn't ready to lead, manage, mentor, or teach. These are the core of any team. They are proficient in their respective language and are probably learning others.

Senior devs are those beyond the bounds of a skillset. They may be leaders, teachers, or mentors in your organization. They can direct the priorities, roadmap, and business related to the development of your product. They are likely proficient in more than one technology, not necessarily other programming languages; perhaps they are familiar with database architecture, search algorithms and science, hardware and scalability, et

xpepper

When you find it difficult to write a concise, focused, isolated test, the production code has unhealthy dependencies to loosen, invert, or break.

Here, “concise” means having no irrelevant details; “focused” means failing for only one reason; “isolated” means executing without side effects on other tests.

(https://thecodewhisperer-blog.tumblr.com/post/333781027/what-your-tests-dont-need-to-know-will-hurt-you)

xpepper

My notes on the video series "London vs Chicago TDD styles" by Uncle Bob And Sandro Mancuso

The git repo of the kata is here: https://github.com/sandromancuso/cleancoders_openchat/

The "starting-point" branch is where both implementations began: https://github.com/sandromancuso/cleancoders_openchat/tree/starting-point

• The 🇬🇧 "openchat-outside-in" branch captures the tomato by tomato history of the London approach.
• The 🇺🇸 "openchat-unclebob" branch captures the tomato by tomato history of the Chicago approach.

What I like about Sandro's style 👍

xpepper

Mac OS X

Mensch coding font

Apps

• Webkit
• Chrome
• Firefox
• Opera