Robert Stoll
Robert Stoll
We want to move away from Spek as test-runner as we consider this project dead and it makes more and more problems in conjunction with intellij and gradle. Hence, we...
*Platform* (all, jvm, js): all *Extension* (none, kotlin 1.3): none ## Code related feature We have samples for api-fluent: ch.tutteli.atrium.api.fluent.en_GB.samples.IterableLikeToContainInOrderOnlyGroupedCreatorSamples and we would like to copy & adopt them to...
*Platform* (all, jvm, js): all *Extension* (none, kotlin 1.3): none ## Code related feature We want to move away from Spek as test-runner as we consider this project dead and...
*Platform* (all, jvm, js): all *Extension* (none, kotlin 1.3): none ## Code related feature We want to move away from Spek as test-runner as we consider this project dead and...
*Platform* (all, jvm, js): all *Extension* (none, kotlin 1.3): none ## Code related feature We want to move away from Spek as test-runner as we consider this project dead and...
*Platform* (all, jvm, js): all *Extension* (none, kotlin 1.3): none ## Code related feature We want to move away from Spek as test-runner as we consider this project dead and...
Similar to #2038 but simpler. Consider the following: ```bash #!/usr/bin/env bash function sourceOrDie() { source "$@" || exit 1 } # shellcheck will not follow the sourced file sourceOrDie "foo.sh"...
### 🚀 Feature Request There is currently no way to define multiple times the same header in route.fulfill. I first hoped I could trick it by using different cases but...
### Version 1.49.0 ### Steps to reproduce kotlin code: ``` page.route({ it.startsWith(url}) { route -> val response = route.fetch() route.fulfill(Route.FulfillOptions().setResponse(response)) } ``` ### Expected behavior I expect that the response...
There are two aspects I would like to reuse of the MethodSource annotation mechanism: 1. the logic to find a suiting method (implemented in MethodArgumentsProvider.findMethod) 2. The tooling support associated...