The second example in section 1.1 says:

expect(result.approved).to.be.false;

It should be:

expect(result.approved).to.be.true;

(I'm guessing you made it false so you could simulate the error output in the next picture.)

Hello! The documentation appears to indicate that Format can be specified on the command line for the VSTest integration (see https://github.com/tonerdo/coverlet/blob/master/Documentation/VSTestIntegration.md#coverlet-options-supported-by-vstest-integration), but it provides no examples on how to do so and I've had zero luck figuring it out myself. Assuming that is indeed possible, would someone b

Hello, and thank for this module.
I am wondering if consideration has been given to adding colour to the stack traces printed out upon failure of a test. For a test runner emphasizing colour, this seems like an obvious omission. I have patched in this functionality using pygments in my fork: psacawa/green@1922bc8 in an ad hoc fashion t

https://docs.nose2.io/en/latest/configuration.html#configuration-files is missing a bit of crucial information: what is the name of the .ini file? It looks like it can be both "unittest.cfg" or "nose2.cfg" if I read the code. Is this correct?

We are trying to migrate from MSTestV1 to MSTestV2. While doing so we noticed the behavior change documented in DeltaWithMSTestV1 - Behavior change 12 which leads to some trouble.

Unfortunately, we did not find any way to limit the execution time of the ClassInitialize and AssemblyInitialize methods.

In a

Add how-to documentation for inequalities.

Should demonstrate:

• using validate.interval() to create left- and right-bounded intervals (for greater-than-or-equal-to and less-than-or-equal-to)
• using functions for implementing greater-than or less than (but not equal-to)
• and maybe interval disjunction (e.g. a combined x < min or max < x)

On SDK documentation it is said that for example with Delete message Target of InputParameters is EntityReference. I've seen on few occasions developers forgetting this when implementing unit tests and they've used Entity type instead of EntityReference.

Borrowing from Fluent Assertions, it would be quite convenient to have lambda-based assertions for collections:

class Thing(val name)
val collection = arrayListOf(Thing("a"), Thing("b"), Thing("c"))

collection.should.contain({ it.name == "a" })

Currently it's possible to replicate this using list extensions,

Hello!

In your README, you use the function patch

    user_objects = patch('django.contrib.auth.models.User.objects', users)

without importing it. It is a bit confusing for people who just started digging into Django testing.

Thanks.

When using quotes inside here doc in the context of fake, the quote will disappear from the output of the faked function. This is different from what is expected from using here doc.

Here is an exemple:

test_should_succeed_but_will_fail() {
  fake toto <<EOF
"test"
EOF

  assert 'toto | grep \"' 'should have found quote but seems like fake swallowed it'
}

test_will_succee

I'm not sure if I've stumbled into a real issue, or just fallen into a documentation hole.

I had a bear of a time getting travis-ci set up this time. When I use run_tests --coverage, I get a timeout waiting for ST3 to respond. When I use run_tests without coverage, they run fine. The raw logs for both runs show the bootstrap installing sublime-coverage:

...
Running command: bootstrap