sbt/sbt-app/src/sbt-test/tests/setup-cleanup/changes/setup.sbt

Test / testOptions += {
  val baseDir = baseDirectory.value
  Tests.Setup { () =>
    IO.touch(baseDir / "setup")
  }
}

Test / testOptions += {
  val t = baseDirectory.value / "tested"
  val c = baseDirectory.value / "cleanup"
  Tests.Cleanup { () =>
    // assert(t.exists, "Didn't exist: " + t.getAbsolutePath)
    IO.delete(t)
    IO.touch(c)
  }
}
scripted tests 2023-01-20 03:37:53 +01:00			`Test / testOptions += {`
Improve if check and prohibit value inside anon This commit does the following things: * Removes the boolean from the instance context passes to the linter. * Prohibits the use of value inside anonymous functions. * Improves the previous check of `value` inside if. The improvements have occurred thanks to the fix of an oversight in the traverser. As a result, several implementation of tasks have been rewritten because of new compilation failures by both checks. Note that the new check that prohibits the use of value inside anonymous functions ignores all the functions whose parameters have been synthesized by scalac (that can happen in a number of different scenarios, like for comprehensions). Other scripted tests have also been fixed. Running `.value` inside an anonymous function yields the following error: ``` [error] /data/rw/code/scala/sbt/main-settings/src/test/scala/sbt/std/TaskPosSpec.scala:50:24: The evaluation of `foo` inside an anonymous function is prohibited. [error] [error] Problem: Task invocations inside anonymous functions are evaluated independently of whether the anonymous function is invoked or not. [error] [error] Solution: [error] 1. Make `foo` evaluation explicit outside of the function body if you don't care about its evaluation. [error] 2. Use a dynamic task to evaluate `foo` and pass that value as a parameter to an anonymous function. [error] [error] val anon = () => foo.value + " " [error] ^ ``` 2017-05-25 15:19:35 +02:00			`val baseDir = baseDirectory.value`
scripted tests 2023-01-20 03:37:53 +01:00			`Tests.Setup { () =>`
[2.x] fix: Invalidate testQuick on test argument changes (#7680) Problem testQuick currently does not invalidate on argument changes. Solution This includes test argument digests. --------- Co-authored-by: adpi2 <adrien.piquerez@gmail.com> 2024-09-17 23:48:53 +02:00			`IO.touch(baseDir / "setup")`
scripted tests 2023-01-20 03:37:53 +01:00			`}`
Improve if check and prohibit value inside anon This commit does the following things: * Removes the boolean from the instance context passes to the linter. * Prohibits the use of value inside anonymous functions. * Improves the previous check of `value` inside if. The improvements have occurred thanks to the fix of an oversight in the traverser. As a result, several implementation of tasks have been rewritten because of new compilation failures by both checks. Note that the new check that prohibits the use of value inside anonymous functions ignores all the functions whose parameters have been synthesized by scalac (that can happen in a number of different scenarios, like for comprehensions). Other scripted tests have also been fixed. Running `.value` inside an anonymous function yields the following error: ``` [error] /data/rw/code/scala/sbt/main-settings/src/test/scala/sbt/std/TaskPosSpec.scala:50:24: The evaluation of `foo` inside an anonymous function is prohibited. [error] [error] Problem: Task invocations inside anonymous functions are evaluated independently of whether the anonymous function is invoked or not. [error] [error] Solution: [error] 1. Make `foo` evaluation explicit outside of the function body if you don't care about its evaluation. [error] 2. Use a dynamic task to evaluate `foo` and pass that value as a parameter to an anonymous function. [error] [error] val anon = () => foo.value + " " [error] ^ ``` 2017-05-25 15:19:35 +02:00			`}`
Apply setup and cleanup hooks to forked tests. The actual class loader for test classes cannot be provided because it is in another jvm. 2013-07-16 19:55:10 +02:00
scripted tests 2023-01-20 03:37:53 +01:00			`Test / testOptions += {`
			`val t = baseDirectory.value / "tested"`
			`val c = baseDirectory.value / "cleanup"`
			`Tests.Cleanup { () =>`
[2.x] fix: Invalidate testQuick on test argument changes (#7680) Problem testQuick currently does not invalidate on argument changes. Solution This includes test argument digests. --------- Co-authored-by: adpi2 <adrien.piquerez@gmail.com> 2024-09-17 23:48:53 +02:00			`// assert(t.exists, "Didn't exist: " + t.getAbsolutePath)`
			`IO.delete(t)`
			`IO.touch(c)`
scripted tests 2023-01-20 03:37:53 +01:00			`}`
Improve if check and prohibit value inside anon This commit does the following things: * Removes the boolean from the instance context passes to the linter. * Prohibits the use of value inside anonymous functions. * Improves the previous check of `value` inside if. The improvements have occurred thanks to the fix of an oversight in the traverser. As a result, several implementation of tasks have been rewritten because of new compilation failures by both checks. Note that the new check that prohibits the use of value inside anonymous functions ignores all the functions whose parameters have been synthesized by scalac (that can happen in a number of different scenarios, like for comprehensions). Other scripted tests have also been fixed. Running `.value` inside an anonymous function yields the following error: ``` [error] /data/rw/code/scala/sbt/main-settings/src/test/scala/sbt/std/TaskPosSpec.scala:50:24: The evaluation of `foo` inside an anonymous function is prohibited. [error] [error] Problem: Task invocations inside anonymous functions are evaluated independently of whether the anonymous function is invoked or not. [error] [error] Solution: [error] 1. Make `foo` evaluation explicit outside of the function body if you don't care about its evaluation. [error] 2. Use a dynamic task to evaluate `foo` and pass that value as a parameter to an anonymous function. [error] [error] val anon = () => foo.value + " " [error] ^ ``` 2017-05-25 15:19:35 +02:00			`}`