Verified Commit 94c6fad2 authored by 35V LG84's avatar 35V LG84
Browse files

Fix silly BuildInfoTest from failing after every new year

This fixes silly BuildInfoTest which fails after every new year,
if test has not been updated. Let's figure a better fix before
year 2100.

Ref: #1

Signed-off-by: 35V LG84's avatar35V LG84 <35vlg84-x4e6b92@e257.fi>
parent 9dd1cc8f
Pipeline #44034590 passed with stage
in 6 minutes and 51 seconds
......@@ -18,7 +18,7 @@ New features in this release are:
==== Fixes
None
* Fix failing test: e257/accounting/tackler#1
==== Development
......
......@@ -23,7 +23,7 @@ class BuildInfoTest extends FlatSpec {
behavior of "BuildInfo"
it should "builtAtString" in {
assert(BuildInfo.builtAtString.startsWith("2019"))
assert(BuildInfo.builtAtString.startsWith("20"))
}
it should "scalaVersion" in {
......
......@@ -8,6 +8,20 @@ Tackler build is done by link:http://www.scala-sbt.org/[sbt].
sbt clean test
=== Running tests
Some of the tests generate lots of output,
especially `cli/test` (test `fi.e257.tackler.cli.TacklerCliTest`).
It might be helpful to run tests selectively, especially in case of errors:
Start `sbt` and run on sbt shell:
....
> apiJVM/test
> core/test
> cli/test
....
== Generating binaries
sbt cli/assembly
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment