Because honestly, what does "new config" even mean? Nobody knows unless
they also know the implementation (which ties a boolean value to an
annotation named "NewConfig") so stating clearly in which scenarios the
tests are running is preferrable. Like, by A LOT.
- fun `config-not-read event is sent to event bus when new config is true`() {
+ fun `config-not-read event is sent to event bus when config file is invalid`() {
File("sone.properties").deleteAfter {
writeText("Invalid")
val configNotReadReceived = AtomicBoolean()
File("sone.properties").deleteAfter {
writeText("Invalid")
val configNotReadReceived = AtomicBoolean()
- fun `config-not-read event is not sent to event bus when first start is true`() {
+ fun `config-not-read event is not sent to event bus when config file does not exist`() {
File("sone.properties").delete()
val configNotReadReceived = AtomicBoolean()
runSonePluginWithRealInjector {
File("sone.properties").delete()
val configNotReadReceived = AtomicBoolean()
runSonePluginWithRealInjector {
- fun `config-not-read event is not sent to event bus when new config is false`() {
+ fun `config-not-read event is not sent to event bus when config file is valid`() {
File("sone.properties").deleteAfter {
writeText("# comment")
val configNotReadReceived = AtomicBoolean()
File("sone.properties").deleteAfter {
writeText("# comment")
val configNotReadReceived = AtomicBoolean()