You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the default factory (in SpekTestEngine) assumes that the spek has a primary constructor that is a no-arg constructor. This can be replaced by: spek.objectInstance ?: spek.constructors.first { it.parameters.isEmpty }.call() to allow for secondary constructors.
My use case is that I want to be able to use the case standalone and included in another spek. When included I want to reduce the amount of test cases it generates (by default 6327 tests - mostly on different data) such as to reduce test time (btw. it seems that test execution has quite a number of bottlenecks).
The text was updated successfully, but these errors were encountered:
Currently the default factory (in SpekTestEngine) assumes that the spek has a primary constructor that is a no-arg constructor. This can be replaced by: spek.objectInstance ?: spek.constructors.first { it.parameters.isEmpty }.call() to allow for secondary constructors.
👍
My use case is that I want to be able to use the case standalone and included in another spek. When included I want to reduce the amount of test cases it generates (by default 6327 tests - mostly on different data) such as to reduce test time (btw. it seems that test execution has quite a number of bottlenecks).
Would be nice if you could describe those bottlenecks in another ticket? :)
Currently the default factory (in SpekTestEngine) assumes that the spek has a primary constructor that is a no-arg constructor. This can be replaced by:
spek.objectInstance ?: spek.constructors.first { it.parameters.isEmpty }.call()
to allow for secondary constructors.My use case is that I want to be able to use the case standalone and included in another spek. When included I want to reduce the amount of test cases it generates (by default 6327 tests - mostly on different data) such as to reduce test time (btw. it seems that test execution has quite a number of bottlenecks).
The text was updated successfully, but these errors were encountered: