IntegrationTesterBase

mill.testkit.IntegrationTesterBase

Attributes

Source
IntegrationTesterBase.scala
Graph
Supertypes
class Object
trait Matchable
class Any
Known subtypes

Members list

Value members

Abstract methods

def cleanupProcessIdFile: Boolean

Attributes

Source
IntegrationTesterBase.scala
def daemonMode: Boolean

Attributes

Source
IntegrationTesterBase.scala
def propagateJavaHome: Boolean

Attributes

Source
IntegrationTesterBase.scala

Attributes

Source
IntegrationTesterBase.scala

Concrete methods

def initWorkspace(): Unit

Initializes the workspace in preparation for integration testing

Initializes the workspace in preparation for integration testing

Attributes

Source
IntegrationTesterBase.scala
def millTestSuiteEnv: Map[String, String]

Attributes

Source
IntegrationTesterBase.scala
def removeProcessIdFile(): Unit

Remove any ID files to try and force them to exit

Remove any ID files to try and force them to exit

Attributes

Source
IntegrationTesterBase.scala

Abstract fields

val baseWorkspacePath: Path

Attributes

Source
IntegrationTesterBase.scala

Concrete fields

val workspacePath: Path

The working directory of the integration test suite, which is the root of the Mill build being tested. Contains the build.mill file, any application code, and the out/ folder containing the build output

The working directory of the integration test suite, which is the root of the Mill build being tested. Contains the build.mill file, any application code, and the out/ folder containing the build output

Each integration test that runs in the same baseWorkspacePath is given a new folder for isolation purposes; even though we try our best to clean up the processes and files from each Mill run, it still doesn't work 100%, and re-using the same folder can cause non-deterministic interference and flakiness

Attributes

Source
IntegrationTesterBase.scala