This is a great book and I've enjoyed following it through almost to the end.

However, if I type / copy the code in the first code block at https://quii.gitbook.io/learn-go-with-tests/go-fundamentals/math#write-the-test-first then run the test, it will give me a

Success: all tests pass.

It looks like the package that is being included already has the correct code. The guide should sure

As a new end user, I cannot find a single user guide or decent documentation. The javadoc reads like it's written as a quick review for someone who already knows the ins/outs of Mockito and just need some sample code. I don't even know what or how Mockito works and the first couple of lines are talking about "mockito inline".

Most open source projects have really great user guides and document

Describe the bug
When the (string) representations of the expected outcome and the actual outcome of e.g. assert.calledWith() are equal, the resulting error message is very confusing and hinting at a bug in the display logic. Instead of <red>actual</red> <green>expected</green> (with <color>...</color> my attempt at showing the expected terminal output color), it displays `actual

Hi,

I think I may have stumbled upon a bug.

With the value to set 'Cart' it shows 'Gear' in the drawer, this happens consistently throughout all other values
<img width="411" alt="image" src="https://user-images.githubusercontent.com/20213078/4796

The reference implementation for Gherkin has adopted 'Cucumber expressions' which are a type based argument substitution in step definitions, similar to ours but using a different syntax. Ref. https://cucumber.io/docs/cucumber/cucumber-expressions/

We currently allow this transformation in step definitions (ref #863):

@Then I should be a user named :name

In order to increase com

When running build.ps1 -t Test, the following output describes the failing tests:

1. Failed : NUnit.Framework.Api.FrameworkControllerTests.ExploreTestsAction_FileNotFound_ReturnsNonRunnableSuite
   Expected: String containing "The system cannot find the file specified."
   But was: "Le fichier sp├®cifi├® est introuvable. (Exception from HRESULT: 0x80070002)"
   at NUnit.Framework.Api.Framew

Summary

The documentation "activate_announcer_on_command_failure" is not helpful for users as it misses information a

In our tests we often validate default data and prop values for the component under test using something like this:

componentUnderTest.data().should.deep.equal({
 // all expected data values go here
});

componentUnderTest.propsData().should.deep.equal({
 // all expected props values go here
});

We're using v4.2.0 and this works nicely for calls to data(), and it do

When Firefox renders a button, by default it adds 2px of padding inside the button. (See this StackOverflow post.)

Add a browser detect for this scenario.

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

Righ now we have a Java sample app, we should show the usage of the app in a Kotlin example also.

Document how to configure JGiven using the JGivenConfiguration annotation.

Bandit needs a logo. The automatically generated avatar on GitHub always reminds me of that.

My initial idea was to combine the hexagon of the C++ logo, a bandit mask and a BDD cycle in one logo. The [result of my first attemp

I am following this tutorial as I get to the step of creating the files when I go to the terminal they already exist.
How or where should I create the three files?

![Screen Shot 2020-02-01 at 12 22 34](https://user-images.githubusercontent.com/27420533/

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.

Versions:
serverless: 1.21.1
serverless-mocha-plugin: 1.7.0

Problem:
I just followed the documentation to add tests to my existing serverless project. I use sls invoke test -p . to run tests and get the following error:

Aruns-MacBook-Pro:aws arunshankar$ sls invoke test -p .
Serverless: Invoke invoke:test
 
  Error --------------------------------------------------
 
  C

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

It should perhaps only be required to install pytest if pytest is going to be used, in which case, imports should be conditional?

I'm not sure it is that much of a big deal, but people do tend to prefer limiting requirements.