Package: testyoke
testyokeProvide insights on the outcomes of software test cases for any programming
language.This project will provide resources to log the results of your test suites and aims
to add useful insights to your testing. Tests are seen as gold, but how do you prune
invalid, ineffective, or plain inaccurate test cases? With TestYoke you can:See the results of tests on this git sha previously.
Big time savings here, by not running again.Flaky Tests - have both passed and failed on the present sha.
There probably is a data or service dependency issue.Bad Tests - tests that have been failing across consecutive shas.If these have been deployed anyways, these tests are worthless. 
Prompt user to delete because they are costing the staff more than a good test is worth.Regressions - tests that failed, were fixed, and fail again in different shas. 
Regressions are recurring issues. They may prompt priority to fix.The HTTP service in this project can run in the background and receive results of
your test running, however you run them.The service presently accepts junit xml, and there is a good chance your testing framework
can export that format.  Try setting up posting the results of your tests after every run
of the suite via your build process.installpip install testyokegetting startedYou will need a server to report metrics to. See "Run the Service."testyoke wrapperA test suite wrapper is in progress. It presently supports pytest only.testyoke pytestmany frameworksThetestyokewrapper supports many testing frameworks. You may
manually specify the framework you're using by supplying theFRAMEWORKenvironment variable.FRAMEWORK=rspec testyoke rspecRun the Service YourselfRun theservice. Default port is 7357, but you may set it with theYOKE_PORTenv var.python3 -m testyoke.server YOKE_PORT=7357Everytime you run a test,POSTthe results using theclient.python -m testyoke.client --sha=`git rev-parse HEAD` --report=junit.xmljunit.xmlis presently the de facto format, as it is one of the more prevalent formats
in the space. It is supported bypytest,scalatest,
and obviously in java frameworks as well.  This is the first format to be supported, but
more formats are expected to be supported soon.You can submit via curl/HTTP Post via theclient, or by curls
(Run this after your tests run):curl -H "vc-sha: $(SHA)" -H "Content-Type: application/xml+junit" -X POST -d @target/path/to/JUNIT.xml http://localhost:7357/projects/testharness/reportsGet reports by:curl http://localhost:7357/projects/testharness/shas/$(GIT_SHA)AnalyticsRun this before your tests run.This will provide you with historical information. If the SHA has previously been proven, it will be reported it asclean.python -m testyoke.client --sha=`git rev-parse HEAD`Example output:###################################################
#
# nature: untested.  fails 0, passes 0
#
###################################################NatureThis is a classification of the SHA you are running on.untested- testyoke hasn't seen results from this SHA yetclean- testyoke has never seen a failure on this SHAbroken- this SHA has never passed completely.flaky- there is at least one flaky test, defined as having passed and failed on the same SHA.ComponentsHTTP servicereportersscalatestpytestrspeccli clientanalyticsweb portalArchAPI -> persist
analyzers