The Wayback Machine - https://web.archive.org/web/20200614100308/https://github.com/topics/testing-framework
Skip to content
#

testing-framework

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 462 public repositories matching this topic...

kylef
kylef commented Dec 11, 2019

This is more of a development problem and does not affect users as it is with dev dependencies. When cloning the repository and running yarn, yarn warns about incorrect peer dependencies:

$ git clone https://github.com/apiaryio/dredd.git dredd-clean
Cloning into 'dredd-clean'...
remote: Enumerating objects: 54, done.
remote: Counting objects: 100% (54/54), done.
remote: Compressin
molecule
ssbarnea
ssbarnea commented Feb 26, 2020

We need to build a multi-dimensional support matrix which would document what is supported , tested or broken, including:

  • operating system
  • installation method pip user, pip-virtualenv, docker-image,...
  • python version
  • ansible version
  • provider (including external ones)
  • verifier

Ideally we should find a way to build this dynamically but for start even a manual table would be us

eyalroz
eyalroz commented Mar 2, 2020

I couldn't find this in the documentation or the FAQ: Is it possible to obtain the current test case's name from within that testcase's code? I mean, it should be, but how do we do it? That should be either in the FAQ or in some other relevant documentation file, IMHO.

kenjiuno
kenjiuno commented Jun 12, 2019

I can obtain record list (in JSON) from server.
jsonTypes handler passes if record list is filled with designated items.
However jsonTypes handler seems to disallow empty record list: Expected '*' not found (path 'records.*')

repro/test.js:

const frisby = require('frisby'),
  Joi = frisby.Joi;

it('should pass', (done) => {
  frisby.fromJSON({ records: [] })
    .inspectBody()
aaronsteers
aaronsteers commented Feb 7, 2020

** Question : **

I arrived here and am interested in leveraging this platform in addition to and as a compliment terratest, but I don't want to start from scratch in writing features and I can't find any reference at all in the readme to a sample library or folder of already-existing tests/features. I could copy-paste all the examples from the .md example files but that seems like more work

GrosQuildu
GrosQuildu commented Feb 19, 2020

Each fuzzer executor (frontend) implements populate_stats method that changes fuzzer-specific output information to the uniform one. That is, it's populate self.stats dictionary.

Currently only AFL provides reasonable amount of runtime informations that are easily accessible and therefore used by the deepstate. Also we scan CRASH_DIR and count amount of crashes found. But other tools ne

airframe
uarlouski
uarlouski commented Jan 28, 2020

Is your feature request related to a problem? Please describe.
If we got an error that some file doesn't exists in FS it would be convenient if that error shows at which parts of the path files become unexistent

Describe the solution you'd like
/path1/path2/path3/path4/file.ext
So if the file path becomes invalid starting from path3, I want this to be included as a part of the error

kelliott55
kelliott55 commented May 15, 2019

We are missing some report focused assertions.
The assertion itself needs implementing and then support in the GUI & PDF reports too.

  1. Markdown: accepts a snippet of markdown formatted text that will be rendered on the output report
  2. Graph: used for plotting data sets from a test execution for vizualization in the report. NB a contender is javascript flot but lets consider alternatives
Wikipedia
Wikipedia
You can’t perform that action at this time.