How much IDEA can help us with Java-Spock

Introduction

The other day, at the company, a topic like "What does the IDE refactoring tool do when writing in Java test Spock?" Came up, so I looked it up. Please let us know if there are any mistakes or stories like "I wish I could do this in such a case!"! !!

Setting up: Writing Java tests in Spock

Writing Java tests in another language in the first place?

JUnit is a well-known Java testing framework, but you may encounter some difficult cases when considering maintainability. Therefore, even for services implemented in Java, you have the option of writing test cases in other languages. There is a lot of controversy around here [^ 1], and one example is the topic of writing Java tests in Spock.

What is Spock

A testing framework implemented in Groovy. Groovy has some enthusiastic users [^ 2], for example Jenkins' father Kawaguchi said ["It's no longer possible not to write JUnit tests in Groovy"](http://d.hatena.ne. jp / kkawa / 2011212).

Spock makes full use of Groovy's features and allows you to write more concisely than JUnit. For writing Java code in Spock, see Qiita Articles and Books -with-spock) etc. are coming out, and I think that it will increase further in the future.

• http://spockframework.org/

How much you can borrow the power of the IDE

Now, when writing Java tests in Groovy, the issue is how much the IDE can be on your side. Because Groovy is a dynamic language, it's easy to imagine situations where automatic method signature changes don't work [^ 3]. This time it is a report that I examined it. The IDE used this time is tried with IntelliJ IDEA 2016.3.4.

Java-Spock with IDEA

Code to use this time

This time, I will try various things using TDDBC github code.

Production code is Java

public class SampleOfJava {

    public String say() {
        return "Hello TDD BootCamp!";
    }

}

The test code is Groovy(Spock)

class SampleSpec extends Specification {

    def "should return 'Hello TDD BootCamp!' in Java"() {

        given:
        def sut = new SampleOfJava()

        when:
        String actual = sut.say()

        then:
        actual == 'Hello TDD BootCamp!'

    }

}

Method rename

First, let's rename a method that you will often use. Let's rename the say method. You can use shift + F6.

rename

    public String shout() { //I renamed it to shout
        return "Hello TDD BootCamp!";
    }

The test code was also renamed automatically.

        given:
        def sut = new SampleOfJava()

        when:
        String actual = sut.shout() //Renamed

        then:
        actual == 'Hello TDD BootCamp!'

First of all, there is no problem.

Signature changes

Next, try changing the signature. The refactoring screen opens with command + F6, so try adding multiple parameters as shown below.

Of course, the signature of the production code has been changed.

Signature changes

    public String say(String addedString, Integer addedInteger) { //Add two arguments
        return "Hello TDD BootCamp!";
    }

The signature of the test code has also changed. But it's not very polite. .. ..

        when:
        String actual = sut.say(,) //Arguments have been added, but I feel like I want you to do something a little more

If you don't like this, it's a little better to include the Default value that you can enter on the refactoring screen earlier.

        when:
        String actual = sut.say("DEFAULT", i) //If you put the default value, it looks a little more like that

I'd like another voice, but let's do it.

Be careful when adding only one argument

I was trying and noticed a tricky part. That is when changing the signature and increasing the argument by only one </ b>. For example, when I increased the arguments with the refactoring tool as shown below, the production code changed.

    public String say(String anotherParameter) { //Arguments added
        return "Hello TDD BootCamp!";
    }

        when:
        String actual = sut.say() //Arguments do not increase orz

        when:
        String actual = sut.say(null) //Null is automatically assigned