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 12,147 public repositories matching this topic...
-
Updated
Oct 23, 2021 - JavaScript
Describe the bug
When running yarn build
and pressing enter, it states the following error:
It would be nice if the tool did not allow empty selections.
To Reproduce
- Run
yarn build
- Press enter
System
Please paste the results of npx sb@next info
here
https://github.com/facebook/jest/blob/0e0eeed9d794fe0d6d7e84f555d9684f9e944221/packages/jest-types/src/Config.ts#L149
https://github.com/facebook/jest/blob/0e0eeed9d794fe0d6d7e84f555d9684f9e944221/packages/jest-config/src/normalize.ts#L364-L371
This isn't actually a name, it's used as an ID. We have displayName
which should be used for e.g. selecting which project to run
-
Updated
Oct 31, 2021 - Python
-
Updated
Nov 1, 2021 - JavaScript
Is your feature request related to a problem? Please describe.
Mostly maintainability and code readability. When you make a change to any of these renderers you are forced to copy the same code more than three times
Describe the solution you'd like
A global component for rendering the response that receives as inputs:
- The response
- List of actions and a callback for each of the
-
Updated
Nov 1, 2021 - JavaScript
-
Updated
Oct 29, 2021 - JavaScript
-
Updated
Oct 13, 2021 - JavaScript
-
Updated
Oct 31, 2021 - JavaScript
-
Updated
Oct 31, 2021 - Go
-
Updated
Oct 31, 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
Oct 20, 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,
Describe the bug
when I turn on CATCH_CONFIG_DISABLE, all CAPTURE(i,j) , i.e. more than one arg will err.
Expected behavior
No such error
Reproduction steps
Build below code with -DCATCH_CONFIG_DISABLE
#include "catch.hpp"
TEST_CASE("generators") {
auto i = GENERATE(as<std::string>(), "a", "b", "c");
SECTION("one") {
auto j = GENERATE(range(8, 11
-
Updated
Oct 3, 2021 - JavaScript
- 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
Oct 31, 2021 - Java
-
Updated
Oct 29, 2021 - JavaScript
-
Updated
Oct 31, 2021 - Nunjucks
-
Updated
Oct 31, 2021 - JavaScript
-
Updated
Nov 1, 2021 - Python
Problem this feature will solve
Given:
FactoryBot.define do
user(factory: :author) { association(:author, role: role) }
end
DefinitionProxy#method_missing
will declare the [association](https://github.com/thoughtbot/factory_bot/blob
-
Updated
Oct 11, 2021 - TypeScript
-
Updated
Oct 18, 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