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 11,329 public repositories matching this topic...
-
Updated
Jul 18, 2021 - JavaScript
Describe the bug
Hi I can't see any debug webpack output despite the option in the build-storybook --help
section:
--debug-webpack Display final webpack configurations for debugging purposes
It's never displayed and there's no txt log in the output directory either...
❯ npx build-storybook --debug-webpack
info @storybook/react v6.3.4
info
info => Cleaning out
🚀 Feature Proposal
From #10123.
When we find a config file, we should also check if there is a jest
entry in any sibling package.json
and print a warning that it is ignored.
If using --config
we should not warn.
Motivation
Helps the user have correct and consistent
-
Updated
Jul 19, 2021 - JavaScript
-
Updated
Jul 18, 2021 - Python
Is your feature request related to a problem? Please describe.
I try to execute my first GET request and get this result:
I think the first-time-user experience could get improved here.
The hint to F12 vanishes soon, and I think accessing the error message via F12 is not a
-
Updated
Jul 19, 2021 - TypeScript
-
Updated
Jul 18, 2021 - JavaScript
-
Updated
Jul 17, 2021 - JavaScript
-
Updated
Jul 10, 2021 - JavaScript
Are you creating an issue in the correct repository?
- When in doubt, create an issue here.
- If you have an issue with the Jasmine docs, file an issue in the docs repo
here: https://github.com/jasmine/jasmine.github.io - This repository is for the core Jasmine framework
-
If you are using a test runner that wraps Jasmine, consider filing an issue with that library if appropriate:
-
Updated
Jul 15, 2021 - JavaScript
@benoittgt very kindly submitted a PR to fix some spacing issues in the markdown using gofmtmd.
It should be possible to automate this as part of the build script
-
Updated
Jul 16, 2021 - Go
Hi,
It seems like the HTTP Assert package does not allow me to specify a body to pass in a POST request for example. Looking at the HTTPBody()
function, the body argument is set to nil
:
req, err := http.NewRequest(method, url+"?"+values.Encode(), nil)
Is this by design, or am I looking at a missing feature?
Cheers,
Description
I have a hardware abstraction layer interface, as well as a driver interface. I have multiple drivers utilizing the HAL interface, while implementing the driver interface. This plugin approach causes me to have identically named tests across multiple test files.
For example:
TEST_CASE("init() returns `E_HAL_INIT`, when HardwareAbstractionLayer::init() returns an er
- Faker version: 8.1.2
- OS: Windows 10
For locale fr_FR siren() and siret() methods generate incorrect values.
https://faker.readthedocs.io/en/master/locales/fr_FR.html#faker.providers.company.fr_FR.Provider.siren
https://faker.readthedocs.io/en/master/locales/fr_FR.html#faker.providers.company.fr_FR.Provider.siret
A valid SIREN has 9 digits = 8 digits + 1 Luhn Key
A valid SIRET has 14
-
Updated
Jul 8, 2021 - JavaScript
-
Updated
Jul 16, 2021 - Java
-
Updated
Jul 15, 2021 - JavaScript
-
Updated
Jul 18, 2021 - PHP
-
Updated
Jul 17, 2021 - JavaScript
-
Updated
Jul 18, 2021 - Python
-
Updated
Jul 15, 2021 - Ruby
-
Updated
Jul 4, 2021 - TypeScript
-
Updated
Jul 15, 2021 - Go
- Wikipedia
- Wikipedia
Testing apps
Testspace.com
Integrated GitHub test solution for CI Results Dashboard, Reporting, Manual Test Case Management, and Exploratory
BuildPulse
Automatically detect, track, and rank flaky tests so you can regain trust in your test suite
TestQuality
The #1 Test Case Creation and Management for GitHub Workflows