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 10,501 public repositories matching this topic...
-
Updated
Feb 24, 2021 - JavaScript
Currently is you set a component property to an object carrying a BigInt the entire storybook stops functioning. The console logs show an error trying to serialize this object.
Uncaught TypeError: Do not know how to serialize a BigInt
at JSON.stringify (<anonymous>)
(...)
Code sample to help you get the context :
const invitations = {
isLoading: false,
e🚀 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
Feb 24, 2021 - JavaScript
Describe the bug
When I pull the resize button of the code editor, it doesn't the resize the code in the editor.
To Reproduce
Steps to reproduce the behavior:
- Click the resize button on the code editor and drag it down
- The code doesn't resize
Expected behavior
I expected the code to resize as I drag down the button.
Screenshots
If applicable, add screenshots to
-
Updated
Feb 22, 2021 - JavaScript
-
Updated
Feb 15, 2021 - JavaScript
-
Updated
Feb 24, 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
Feb 20, 2021 - JavaScript
-
Updated
Feb 23, 2021 - Go
@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
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 erHi,
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,
-
Updated
Feb 23, 2021 - Java
-
Updated
Jan 1, 2021 - JavaScript
-
Updated
Feb 9, 2021 - JavaScript
-
Updated
Feb 24, 2021 - PHP
-
Updated
Feb 24, 2021 - JavaScript
-
Updated
Feb 21, 2021 - Ruby
-
Updated
Feb 23, 2021 - Python
-
Updated
Feb 23, 2021 - TypeScript
-
Updated
Feb 22, 2021 - Go
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 :)
-
Updated
Feb 11, 2021
- Wikipedia
- Wikipedia
Testing apps
TestQuality
The #1 Test Case Creation and Management for GitHub Workflows
BuildPulse
Automatically detect, track, and rank flaky tests so you can regain trust in your test suite