Skip to content
#

unit-testing

Here are 2,678 public repositories matching this topic...

ava
SwifterSwift
sinon
rensbaardman
rensbaardman commented Sep 19, 2019

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

szegel
szegel commented Mar 26, 2020

According to your documentation (https://docs.pytest.org/en/latest/xunit_setup.html), I can name a method teardown() in a test class, and it should not get run by pytest. I am using version pytest-3.8.2.

Pytest calls a method called teardown on class destruction even though it is specified as teardown_class in your documentation. I am guessing this accidentally did not get removed, when the na

KartikShankhavaram
KartikShankhavaram commented Mar 18, 2020

Description

There aren't enough resources on how to use Shadows in tests, or how they work. Some more documentation would really be helpful to understand and use them quicker.

Steps to Reproduce

None

Robolectric & Android Version

Robolectric 4.3

Link to a public git repo demonstrating the problem:

None

Codeception
kylef
kylef commented Dec 11, 2019

This is more of a development problem and does not affect users as it is with dev dependencies. When cloning the repository and running yarn, yarn warns about incorrect peer dependencies:

$ git clone https://github.com/apiaryio/dredd.git dredd-clean
Cloning into 'dredd-clean'...
remote: Enumerating objects: 54, done.
remote: Counting objects: 100% (54/54), done.
remote: Compressin
GalNoga
GalNoga commented Mar 12, 2019

when upgrading to mocha >3 rewire ruins the code coverge generate by nyc. all works well without using rewire..
node version: 10.15.2
rewire: 4.0.1
nyc: 13.3.0
mocha: works with '3.5.3', fail with ^4,^5,^6
OS: windows, Darwin
command: "nyc --reporter=html --reporter=text ./node_modules/.bin/mocha "./*.spec.js" --timeout=3000"

works with mocha '3.5.3':
![good](https://user-images.github

JeffreyDing11223
JeffreyDing11223 commented Nov 11, 2018

unit test coverage is always 0% , even the log shows that "Linter:UnitTest over".

command:
goreporter -p ./ -r /Users/jeffrey -f html
log:

2018/11/11 19:33:45 The template path is not specified,and will use the default template
2018/11/11 19:33:45 There are no packages that are excepted, review all items of the package
2018/11/11 19:33:45 Linter:CountCode over,time consumi

eyalroz
eyalroz commented Mar 2, 2020

I couldn't find this in the documentation or the FAQ: Is it possible to obtain the current test case's name from within that testcase's code? I mean, it should be, but how do we do it? That should be either in the FAQ or in some other relevant documentation file, IMHO.

cake
fluentassertions
ackginger
ackginger commented Sep 13, 2019

Description

When comparing two identical dictionaries which use an object as the key, .Should().BeEquivalentTo() fails.

If I override .Equals() then it succeeds, which feels like it goes against the principle of equivalence expectations.

Whilst this may be my misunderstanding of the expectation, the docs don't seem to call this limitation out, so perhaps worth documenting if deemed

fast-check
vweevers
vweevers commented Jan 23, 2020

We currently have --list-browsers which lists all available browsers, and when you run airtap, it prints which browsers are actually tested:

$ npm run test-browsers
[secure]@5.0.1 test-browsers /home/travis/build/Level/[secure]
standard && airtap --sauce-connect --loopback airtap.local --coverage test/index.js

  • testing: chrome @ Windows 10: 79
  • testing: firefox @ Windows 10: 7
AnthonyMillerSF
AnthonyMillerSF commented Apr 16, 2020

I have a library that I generate all of my mocks into that is imported in my unit tests. When mocking a protocol, the generated mock object doesn't have an initializer declared. This means is uses the default initializer, which would be fine, except the default init() method is internal. I can get around this by importing my mock library @testable, but I'd suggest that protocol mocks for publi

KantarBruceAdams
KantarBruceAdams commented Jul 10, 2019

Is your feature request related to a problem? Please describe.

I'm trying to get two containers to communicate with each other.
I can start up each container and connect to it from the command line using localhost and the bound IP but I'm not clear how to get two containers to talk to each other.
I think this would be the equivalent of "docker network connect" https://stackoverflow.com/qu

Improve this page

Add a description, image, and links to the unit-testing topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the unit-testing topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.