Kyle Winter

having poked around to trying to decouple from the async tests, I believe the issue is that the current hooks use: `abstract override def run(testName: Option[String], args: Args): Status` which...

took at crack at this, moved TestSuite/TestSuiteMixin to Suite/SuiteMixin: https://github.com/playframework/scalatestplus-play/pull/255

I've been poking around at trying to decouple the tests from sync versions - looks like a potential answer here might be to use BeforeAndAfterAll in the parent suites that...

wanted to get this up for discussion - this should allow users to make use of either sync or async tests, but there is one notable change in behavior: Using...

that could work. also another option: it feels a bit hacky, but overriding testDataFor will allow the cancellation to keep the previous behavior ``` abstract override def testDataFor(testName: String, theConfigMap:...

for now, I've reverted the browser specs back, and added a round 2 on the app/server specs. so this PR in total, for app/server fixtures: * allows use of sync...

another issue popped up - this currently breaks the previous behavior for using ParallelTestExecution with PerSuite, like `extends OneAppPerSuite with ParallelTestExecution` before: results in an app/server being created per test...

I've signed the CLA (a few times) - don't know why it hasn't picked it up If someone can lend some guidance on what to do with the MIMA errors,...

I've associated the commit email with my account - so that's hopefully good to go I think that just leaves the binary compatibility issue from MIMA, and guidance on what...

We've similarly implemented our own backoff - but in a different way. We instead skip Kinesis altogether, log an error, and put the record into a local file that gets...