anchor.diff:  === Coding style
   
   We follow https://github.com/oss-generic/process/blob/master/docs/CodingStandards.md[oss-generic coding standards].
  +
  +=== Configuring import statements
  +
  +IntelliJ uses a different import order from our coding style. To rectify this issue:
  +
  +. Go to `File` > `Settings...` (Windows/Linux), or `IntelliJ IDEA` > `Preferences...` (macOS)
  +. Select `Editor` > `Code Style` > `Java`
  +. Click on the `Imports` tab to set the order
  +
  +* For `Class count to use import with '\*'` and `Names count to use static import with '*'`: Set to `999` to prevent IntelliJ from contracting the import statements
  +* For `Import Layout`: The order is `import static all other imports`, `import java.\*`, `import javax.*`, `import org.\*`, `import com.*`, `import all other imports`. Add a `<blank line>` between each `import`
   
   == Design
   
  
positive.code: 
  Tests can be found in the `./src/test/java` folder.
  
  *In Eclipse*:
  
  * To run all tests, right-click on the `src/test/java` folder and choose `Run as` > `JUnit Test`
  * To run a subset of tests, you can right-click on a test package, test class, or a test and choose to run as a JUnit test.
  
  *Using Gradle*:
  
  
negative.code: 
  Thanks to the https://github.com/TestFX/TestFX[TestFX] library we use, our GUI tests can be run in the _headless_ mode. In the headless mode, GUI tests do not show up on the screen. That means the developer can do other things on the Computer while the tests are running. See <<UsingGradle#running-tests, UsingGradle.adoc>> to learn how to run tests in headless mode.
  
  == Dev Ops
  
  === Build Automation
  