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,850 public repositories matching this topic...
-
Updated
Apr 24, 2021 - JavaScript
What's the problem?
I have successfully customized my storybook with addon-themes and created the dark style for div with a .docs-story class.
I tried to style the "show code" button on the docs tab without luck via CSS in preview-head.html.
The problem is that there is no unique CSS class to scope (only dynamically generated classes):
<div class="css-11xgcgt">
<button c
🚀 Feature Proposal
Currently, pressing Ctrl+u in a watch mode pattern prompt inserts an invisible character that also somewhat breaks searching because the files/tests searched for do not contain the character.
In most terminal environments, Ctrl+u clears the whole line. I think this
-
Updated
Apr 23, 2021 - JavaScript
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
Apr 24, 2021 - JavaScript
-
Updated
Apr 5, 2021 - JavaScript
-
Updated
Apr 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
Apr 23, 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
Apr 11, 2021 - Go
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
Apr 23, 2021 - Java
-
Updated
Apr 3, 2021 - JavaScript
-
Updated
Apr 24, 2021 - JavaScript
-
Updated
Apr 23, 2021 - PHP
-
Updated
Apr 25, 2021 - JavaScript
-
Updated
Apr 25, 2021 - Python
-
Updated
Apr 16, 2021 - Ruby
-
Updated
Apr 4, 2021 - TypeScript
-
Updated
Apr 21, 2021 - Go
With the support of type-hints Python signatures can give information on the type of returned values of a method. This could be used to improve the documentation generated by libdoc.
def my_func(foo: str, count: int) -> str: will give the following in the Argument column:
foo: str, count: int
This could be expanded to include the type of the returned value:
foo: str, count: int -> str
- Wikipedia
- Wikipedia
Testing apps
TestQuality
The #1 Test Case Creation and Management for GitHub Workflows
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
