Skip to content
#

Testing

Testing is the practice of systematically testing software to make sure it works. Testing can be iterative, and happen multiple times.

Eliminate bugs and ship with more confidence by adding these tools to your workflow.

Here are 8,232 public repositories matching this topic...

techsin
techsin commented Apr 22, 2019

Tell us about your environment:

  • Puppeteer version: 1.14
  • Platform / OS version: Windows
  • Node.js version: 10

What steps will reproduce the problem?
try to pass a promise to await page.waitForResponse(response => condition) instead of urlOrPredicate.

What is the expected result?
expect async function to work

What happens instead?
no waiting as promise

storybook
levelingup
levelingup commented Dec 24, 2019

I tried to follow the initial steps from here: https://www.learnstorybook.com/intro-to-storybook/react/en/get-started/

running:

npx create-react-app taskbox
cd taskbox

Then when I ran:
npx -p @storybook/cli sb init

I get the error TypeError: Cannot set property 'storybook' of undefined

This is the full message in my terminal:

 sb init - the simplest way to add a
JKAnderson409
JKAnderson409 commented Jul 25, 2019

Is your feature request related to a problem or a nice-to-have?? Please describe.
I wasted a good deal of time trying to get the "exports" interface (which I think is perfect for organizing tests for a large OOP project) only to find that it just does not work in the browser. I can get my demo test to run on the command line (node) just fine but Firefox and Chromium ignore the exported test s

browne0
browne0 commented Jun 25, 2019

Hello! Big fan of enzyme here.

I use Enzyme a lot for unit testing and I've noticed recently that people are consistently recommending people use instance prop functions versus using the simulate behavior provided by Enzyme because of the bad implementation.

Is there anyway we could get the docs updated with what the preferred solution is? It's not really clear as the docs stand right now.

cypress
ava
novemberborn
novemberborn commented Feb 1, 2020

test.cb() is a legacy API. It can be used for testing callback APIs, but for anything more advanced we'd prefer you use test() with an async function.

We should update the error message here:

https://github.com/avajs/ava/blob/56338dcb77246b5eca3c01e24d1cb6d66da8f71f/lib/test.js#L597

It should say something like:

Use test.cb() for legacy callback APIs. When using promises or asy

postwoman
debjeetsarkar
debjeetsarkar commented Nov 26, 2019

Is your feature request related to a problem? Please describe.
There is no comprehensive tooling while working with MQTT brokers.

Describe the solution you'd like
A simple interface to connect to an MQTT broker.
Subscribe to topics
Publish to topics

Describe alternatives you've considered
MQTT Lens

TimvdLippe
TimvdLippe commented Oct 27, 2017

Per https://blog.jetbrains.com/idea/2017/10/intellij-idea-2017-3-public-preview IntelliJ can now auto-suggest replacements for deprecated methods. Once IntelliJ 2017-3 is published, let's check whether our deprecations satisfy the requirements for this check.

Maybe we can also write a static analysis check that can automatically verify that whenever we deprecated method we:

  1. Link to a replac
lucielavickova
lucielavickova commented Jul 12, 2019

Would it be possible to add "trim" parameter to keyword "Should Be Equal As Strings" (+related keywords)?
Many times I need to compare two strings, but there are some trailing or leading whitespaces in the actual value, which I don't care about, so I always have to trim them before. Having trim as a parameter in these keywords would help me a lot :)

Wikipedia
Wikipedia

Testing apps

PigCI

Monitor Ruby on Rails apps memory & database usage during CI - Spot memory leaks before deploying to production

fuzzit.dev

Continuous Fuzzing for C/C++/Java/Golang/Rust & Swift integrated with your current CI/CD workflow

See more Testing apps
You can’t perform that action at this time.