Saravanan666/pypi-org huggingface dataset:
Package: nose-mp-split
This plugin adds_multiprocess_can_split_ = Trueto each of your test
classes and modules. That’s all. This tells nose’s multiprocess plugin that it
doesn’t need to run all of a class’s tests in the same process. Nose will then
distribute test cases from the same class (or module) across different
processes. It was written in response to behavior demonstratedhere.When it’s safe to use with your tests, this plugin is so cool!There’s no need to edit your tests to contain a nose-specific flag.It evenly distributes test cases (rather than test classes) across processes.
This utilizes worker process better to speed up test runs, especially if one
class has many tests cases and takes much longer to run than the others.It produces more responsive output. Since nose runs testclassesin worker
processes, it waits until each class has finished before printing the results
for that class. This plugin ensures the results of a test case are printed
immediately after that test has finished.You can use this plugin when you know your tests are safe to run in parallel.
For instance, don’t use this plugin if you have test fixtures that cannot
be run repeatedly and concurrently in multiple processes.Quickstart$pipinstallnose-mp-split$nosetests--mp-split-all--processes=4mytests/nose-mp-splithas no effect when not running tests in multiple processes.
Package: nose-mycode
…it knows your code!Nose my code colours your code in a stack traceDo you like running, testing and debugging your code in the command line using nose?Have you ever been the unfortunate reader of a long stack trace?Ever wished the trace output could be a bit more helpful?Tested on Python 2.7, and 3.4 runnin on Linux & OSX. Probably works on other versions
of python. Probably doesn’t work on Windows.Built at the Building Better Tools with Python day, Google Campus London, 7th Feb 2015.To see it in action you can run the test:python test.py –with-mycode
Package: nosenicedots
It’s anosetestsplugin that prints nicer dots grouped by class/module.InstallFrom PyPI:pip install nosenicedotsor from source:pip install -e git+git://github.com/kumar303/nose-nicedots.git#egg=nosenicedotsUsagenosetests --with-nicedotsExample$ nosetests --with-nicedots

apps/devhub/tests/test_views.py:TestActivity
..............
apps/devhub/tests/test_views.py:TestAddVersion
.
======================================================================
FAIL: apps/devhub/tests/test_views.py:TestAddVersion.test_unique_version_num
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/path/to/apps/devhub/tests/test_views.py", line 3132, in test_unique_version_num
    assert 0
AssertionError


apps/devhub/tests/test_views.py:TestCreateFoobar
..
apps/devhub/tests/test_views.py:TestDashboard
.....
apps/devhub/tests/test_views.py:TestDelete
..
======================================================================
FAIL: apps/devhub/tests/test_views.py:TestAddVersion.test_unique_version_num
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/path/to/apps/devhub/tests/test_views.py", line 3132, in test_unique_version_num
    assert 0
AssertionError

----------------------------------------------------------------------
Ran 44 tests in 1.62s

FAILED (failures=1)This new style of output is intended as a more useful test report and is
inspired bypy.test. Instead of a confusing (yet pretty) mess of dots
you’ll see a printout of the module or class followed by dots that indicate
each test in that group.You’ll see the traceback for a failure immediately, which was designed for
long running test suites. Note that the tracebacks are repeated again down at
the bottom in case the output had scrolled off the screen already. Using--stopwill not duplicate failure output.It’s Also A Test AddressEach module or class group also doubles as an argument you can give to Nose if
you want to re-run that group of tests. From the above output you could
copy/paste and re-run tests in the TestActivity class like this:$ nosetests --with-nicedots apps/devhub/tests/test_views.py:TestActivity

apps/devhub/tests/test_views.py:TestActivity
..............
----------------------------------------------------------------------
Ran 14 tests in 0.62s

OKCaveatsIf any other plugin needs to patch the unittest result then it will
conflict with Nice Dots.Python 2.5, 2.6 and 2.7 are supported at the moment. Other versions may or
may not work.  Python 3 isnotyet supported.  There are a few failing
tests.
Package: noseOfYeti
This is a project creates a custom Pythoncodecthat lets the developer write
their tests using anRSpecinspired DSL (i.e.describeanditblocks).It uses the fact that python allows the registration of acodecthat can be used
to read in source code and modify it at import time.NoseOfYeti uses this technique to find files with a particular coding declaration
on the first line of a file to turn the rspec inspired DSL into ordinary python
that is then executed as if it were written like that in the first place.The original idea comes from@fmeyerwho wrote thisblog postand a simpleproof of conceptbefore it was
picked up and worked on by@hltbrainthis repo.@delfickdiscovered this work in 2010 and over the
following decade plus has improved on the concept, giving it more features and
integration with python tooling.The documentation can be found athttp://noseofyeti.readthedocs.ioand the code
over athttps://github.com/delfick/nose-of-yeti.Updating nose-of-yeti versionIt is recommended any .pyc files are removed when NoseOfYeti is upgraded.The Python interpreter skips the translation process if it
sees a .pyc file (unless the .py file has changed since the .pyc file was
created). This means that any changes in the translation process won’t apply
until either the .pyc files are removed or all the .py files have been changed.
Package: noseonalchemist
nose plugin for reporting about commit counts on SQLAlchemyUSAGErun nosetests with--with-commitreport:$ nosetests --with-commitreportyou can get report of commit counts:/path/to/test1.py
tests.test_it commit 2 times
tests.test_it2 commit 11 times

/path/to/test2.py
tests2.test_it commit 2 times
tests2.test_it2 commit 11 times
Package: nose-order-plugin
Nose order pluginThis plugin allows methods in Nose test classes to run in the order they aredefined, rather than alphabetically.Note that it is bad practice to rely on test order. If you can avoid it, do so;otherwise this plugin is for you.INSTALLATIONFrom PyPI: pip install nose_order_pluginFrom source: setup.py installUSAGE- Mark the test class with the nose_order_plugin.ordered decorator- Pass the --with-ordered-tests option to NoseCAVEATS- Only plain classes may be ordered. Classes deriving from unittest.TestCaseare incompatible with this plugin.- The plugin looks at source code lines for ordering; if the methods are notdefined in a single file (or other magic is used), the ordering might not beprecise.- Test generators are not supported -- they might work, but they're untested.DEVELOPMENTThe current maintainer is Petr Viktorin <encukou@gmail.com>The plugin was originally developed as part of the FreeIPA project.Development is done on Github: github.com/encukou/nose-order-pluginIssues and pull requests are welcome.A Github-less workflow is also available:- git clone github.com/encukou/nose-order-plugin- Create a set of patches and mail them to the author,or host a Git branch and send a link to it by e-mail.
Package: nose-parallel
A plugin to help split up your tests runs across multiple machines.In an ideal world, test suites should be fast enough that they can
be run locally on a single machine without extra engineering. This
plugin is there to help when you can’t make that to happen.Thiswon’thelp you run tests in parallel on one machine in different
threads; that’s what the built-inmultiprocessplugin
is for.Thiswillhelp you split up your test suites so that you can run the
suites on multiple machines and not have the same test run twice - think
Jenkins with themultijobplugin, or CI services likeCircleCI.Installpipinstallnose-parallelUsageOn each machine:Export environment variablesNODE_TOTAL(the number of machines on which the suite will be run) and andNODE_INDEX(the 0-based index of the current machine)Run nosetests with the--with-parallelflagDo something to join the results from all the machines back togetherFor example, this is how we’d run nosetests on the second machine in a
four-machine testing cluster:NODE_TOTAL=4NODE_INDEX=1nosetests--with-parallelIf you don’t set those variables,nose-parallelwill do the right thing and run all your tests.
It also supports natively the default environment variables from:CircleCIBuildkiteGitLab CIWe welcome PRs that add native support for other CI alternatives.If you want to further randomize the distribution of tests, so
that the same test cases don’t always run together on the same node, you may
use the--parallel-saltoption orNOSE_PARALLEL_SALTenvironment variable
to specify a salt value for the randomization (e.g. a build number, the day of the month).
The salt must be the same on each node during a parallel build, otherwise some test cases might be missed.For example, on CircleCI you could do:nosetests--with-parallel--parallel-salt-envCIRCLE_BUILD_NUMBy defaultnose-parallelwill split tests based on method and function names. You can customize this strategy by setting the--parallel-strategyoption. Supported strategies are: ‘CLASS’, ‘DIRECTORY’, ‘FILE’, ‘METHOD’, ‘FUNCTION’ and ‘MODULE’.For example, to split tests based on the file names:nosetests--with-parallel--parallel-strategy=FILELicensenose-parallelis released under the MIT license.ContributeCheck for open issues or open a fresh issue to start a discussion around a feature idea or a bug.Fork the repository on GitHub to start making your changes to the master branch (or branch off of it).Send a pull request and bug the maintainer until it gets merged and published.Thanks To@mahmoudimus, whosenose-timerplugin this is based off of
Package: nose-parameterized
DEPRECATION WARNINGThenose-parameterizedpackage is deprecated and has been renamed toparameterized.See:https://pypi.python.org/pypi/parameterizedhttps://github.com/wolever/parameterizedMigrating fromnose-parameterizedtoparameterizedTo migrate a codebase fromnose-parameterizedtoparameterized:Update the requirements file, replacingnose-parameterizedwithparameterized.Replace all references tonose_parameterizedwithparameterized:$ perl -pi -e 's/nose_parameterized/parameterized/g' your-codebase/You’re done!
Package: nose-pathmunge
Project hosting: <http://bitbucket.org/jnoller/nose-pathmunge/>ContentsAboutWhat It DoesUsageCommand line optionsTODOChanges & NewsAboutWritten by Jesse NollerLicensed under the Apache Software License, 2.0You can install it witheasy_installnose-pathmungeWhat It Doesnose-pathmunge is a plugin to the nose test framework which provides a method
to add directories to the sys.path of nose, which is inherited by the tests
running within nose.This itch stems from in many of my own cases, the need to add modules to a
given run (dependencies) that I don’t want to install because they’re synced
from a source control system, and change frequently.This plugin is extremely simple. It’s meant to be.UsageUsage is simple - install the package, and then execute nosetests like this:nosetests --with-path=/home/jesse/src --with-path=/other/dirRemember the rules when appending directories to your path - you should add
the directory above a module - not the module directory itself, and there
needs to be a valid __init__.py file. For example, the following project
layout in subversion:myproj/
    src/
        mymodule/
            __init__.py
            foobar.pyYou would add this like this:nosetests --with-path=/home/jesse/src/myproj/srcThis would addmymodule/...to the sys.path for the tests to be able to
import.Command line optionsAfter it is installed, the plugin adds the following command line flags to
nosetests:--with-path=TESTCONFIG  Additional directories to add to the nose sys.path
                        [NOSE_ADDITIONAL_PATHS]You can pass in as many paths as you like. I suggest 3, as that’s a pleasant
number.TODOVerify works/doesn’t work with multiprocess pluginAdd testsChanges & News0.1.2:Fix PyPI issues; fix easy_install(ability)0.1:Initial release.  May contain bits of glass.
Package: nose-picker
nose-pickeris a plugin that picks a subset of your unit tests (in django
too!)This plugin modifies nose’s unit test discovery to only pick a (1/N) subset of
unit tests to run. By passing in the--total-processesarguments, you pick
the denominator (the N above) which you want to run. The--which-processargument controls which part of that subset to run, so if you had 5 subsets you
could pick 0, 1, 2, 3, or 4.How does it work? Very simple! It hashes the filenames that nose is
running through, does a modulo division by N, then sees if this file is “its”.
Very simple, but it lets you run multiple of thesenose-pickerenabled
runners in parallel, each running a separate subset of the unit tests!MotivationThe nose multiprocess plugin takes over the test runner when it runs, and thus
is not amenable to environments where you need a custom test runner.nose-pickerlets you keep your test runner!InstallingThroughpip:pip install --user nose-pickerSample Multiprocess ScriptSomething like:def main():
    num_processes = int(multiprocessing.cpu_count() * 2.5)
    tests = []
    for i in range(num_processes):
        test_command = TEST_CMD_TEMPLATE % (
            i,
            num_processes,
        )
        tests.append(TestWatcher(test_command))

    returncode = 0
    for test_watcher in tests:
        test_watcher.join()
        if test_watcher.returncode > 0:
            returncode += test_watcher.returncode
        for line in test_watcher.stderr.splitlines():
            if not (
                line.endswith(' ... ok') or
                '... SKIP' in line
            ):
                sys.stderr.write(line + '\n')

    return returncode


class TestWatcher(threading.Thread):
    def __init__(self, command):
        super(TestWatcher, self).__init__()
        self.command = command
        self.stdout = ''
        self.stderr = ''
        self.start()
        self.returncode = 0

    def run(self):
        p = subprocess.Popen(
            self.command,
            shell=True,
            stdout=subprocess.PIPE,
            stderr=subprocess.PIPE,
        )
        self.stdout, self.stderr = p.communicate()
        self.returncode = p.returncodeLicensenose-pickeris copyright 2014 Eventbrite and Contributors, and is made
available under BSD-style license; see LICENSE for details.
Package: nosepride
NoseprideThe colors are stolen from the minitest/pride plugin for minitest. This
plugin also formats traceback and error reports with less visual noise,
this was heavily inspired by rspec’s report output.ScreenshotExample console outputInstallationpip install noseprideUsageNothing! Nosepride is on by default! But if you mush turn it off…nosetests --fabulous-offChangelogVersion 0.1.5Python 3.3 support!Version 0.1.0Plays better with other plugins (the tricky part is to avoid nosetests
regular output to leak out) Show docstring of test when one is available
Fixed bug in traceback printing (was filtering out relative file outputs
when we actually want those)Version 0.0.6Filtering out all path from traceback not directly on project path Empty
error message caused report to have nothing but a blank line, it now
prints the error class nameVersion 0.0.4Better failure formattingLicenseThe MIT License (MIT)Copyright (c) 2014 Hugo BastienPermission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the
“Software”), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Package: noseprogress
================nose-progress================Give your tests a progress before testcase name 3 lines::pip install nose-progresscd your_projectnosetests --with-progressFeatures========Progress Like this------------::(venv) E:\workspace>nosetests -v -s test_case_0000.py --with-schedulingnose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'][1/2] test_case.test_case_0000.test_learn_3 ... ok[2/2] test_case.test_case_0000.test_lear_4 ... okInstallation============::pip install nose-progressiveUpgrading=========To upgrade from an older version of nose-progressive, assuming you didn'tinstall it from git::pip install --upgrade nose-progressUse===The simple way::nosetests --with-schedulingAuthor======landhu, while waiting for tests to complete ;-)Version History===============0.1* Initial release
Package: nose-pudb
The nose-pudb plugin provides the integration between thenosetesting framework and thepudbconsole-based visual debugger.
Instead of collecting and displaying the test results, the test runner can drop into the debugger on test errors and/or failures.This is similar to the nose’s built-inpdbplugin which uses the debugger from the python standard library.Please submit bugs and patches onhttps://github.com/AntoineD/nose-pudb/issues.This plugin has been originally developed byAntti Kaihola.InstallationInstall nose-pudb using pip:$ pip nose-pudbOr you can clone the source usinggitfromhttp://github.com/AntoineD/nose-pudb.gitand install it with:$ python setup.py installUsageTo run nose and drop into pudb on test failures and errors, use:$ nosetests --pudbor set the environment variableNOSE_PUDB:$ NOSE_PUDB=1 nosetestsTo drop into pudb on failures, use:$ nosetests --pudb-failuresor set the environment variableNOSE_PUDB_FAILURES:$ NOSE_PUDB_FAILURES=1 nosetestsTo drop into pudb on errors, use:$ nosetests --pudb-errorsor set the environment variableNOSE_PUDB_ERRORS:$ NOSE_PUDB_ERRORS=1 nosetestsLicenseThis plugin is released under the GNU Lesser General Public license (LGPL).
See the fileLICENSEfor details.
Package: nose-py3
nose extends the test loading and running features of unittest, makingit easier to write, find and run tests.By default, nose will run tests in files or directories under the current
working directory whose names include “test” or “Test” at a word boundary
(like “test_this” or “functional_test” or “TestClass” but not
“libtest”). Test output is similar to that of unittest, but also includes
captured stdout output from failing tests, for easy print-style debugging.These features, and many more, are customizable through the use of
plugins. Plugins included with nose provide support for doctest, code
coverage and profiling, flexible attribute-based test selection,
output capture and more. More information about writing plugins may be
found on in the nose API documentation, here:http://readthedocs.org/docs/nose/If you have recently reported a bug marked as fixed, or have a craving for
the very latest, you may want the development version instead:https://github.com/atsb/nose-py3
Package: nose-quickunit
Given standard test setup, will determine which tests need to run against a given diff.For example, say you’re working in your branch called my-new-sexy-feature, which modifies the following files:src/foo/bar/__init__.py
src/foo/bar/baz.py
src/foo/biz.pyNow if we run with the default options,nosetests--with-quickunit, it will look for tests (by default) in
the following base directories:tests/src/foo/bar/*
tests/src/foo/biz/*(It does this by analyzing the diff againstgit merge-base HEAD master, and determining which files you’ve changed
are tests, including them, and which files containing test coverage in a parallel directory.)NoteAs of 0.5.0 nose-quickunit no longer reports test coverageConfigIf you want to support multiple directories for searching (let’s say you break up unittests from integration tests)
you can do that as well:--quickunit-prefix=tests/unit/ --quickunit-prefix=tests/integration/Or, if you’d prefer, viasetup.cfg:quickunit-prefix = tests/unit
                   tests/integrationOr, viasetup.cfg:quickunit-json = -
Package: nose-rapido
A Nose plugin that allows to get rapid feedback from tests, by filling your terminal either with green (can be changed to blue) or red background, depending on your tests result.Use together with a continuous running test plugin such asnose-watchfor optimal results.Installationpip install nose-rapidoHow to useIn order to use this plugin use the--with-rapidoswitch:nosetests --with-rapidoNOTE:nose-rapido will override any output you have from other plugins.You can also replace the color green for successfull tests to blue (easier to see for colorblinded):nosetests --with-rapido --rapido-blueScreenshotsGoodBadBlueDevelopmentPreferably in a virtualenv:pip install -r requirements-dev.txt
nosetests
Package: nose-regression
How to use regression tests---------------------------**If regression tests are already installed, skip to step 5.1)Create your test files.2)Download the plugin package.3)Change directories into the plugin folder4)Run `pip install -e .'5)Run `nosetests --with-regression' where you would normally runyour nose tests6)???7)Profit while you look at your fancy new reg_settings.pyOutput------At the end of the nosetest output, Nose Regression will print outany tests that used to fail but now pass (if any) and any tests thatshould pass but happened to fail (if any).  All tests are separatedand say which module they're from.Options--------n/--new    Run tests that should fail to quickly see if any testsare now functional-r/--reg    Run tests that shouldn't fail to quickly see if any testsare now broken-W          Don't write to reg_settings.py-f/--file   Specify which reg_settings.py file you want to use(not completely functional)Inside the reg_settings.py file, there's an options dictionary at the top.If you want any options to always run (excluding -f/--file) place the shortoption as the key and any required values as the value. Currently just leavethe value as '' as the only option requiring a value is -f/--file.Notes-----This plugin does not yet fully support methods, only functions. Please notethis when creating tests you want to use with this plugin.Thanks for using it! :)
Package: nose-reorder
A nose plugin to reorder tests by likelihood of failure. This plugin
needs to accessLaunbhableAPI.Install$ pip install nose-reorderUsage$ nosetests --reorderIn addition to specifying the--reorderflag, you need to set the
following environment variables in your environment. These values should
be provided from Launchable.KeyDescriptionLAUNCH
ABLE_REORDERING_AWS_ACCESS_KEY_IDAWS access key id to retrieve a
request template fileLAUNCHABLE
_REORDERING_AWS_SECRET_ACCESS_KEYAWS secret access key to retrieve
a request template fileLAUNCHABLE_REORDERING_API_TOKENAPI token to access Launchable
APILAUNCHABLE_REORDERING_DIR_NAMEDirectory name storing a request
template fileLAUNCHABLE_REORDERING_BASE_URLLaunchable API URLLAUNCHABLE_REORDERING_ORG_NAMELaunchable organization nameLAU
NCHABLE_REORDERING_WORKSPACE_NAMELaunchable workspace nameDevelopmentPull requests are always appreciated. If you want to see whether your
changes work as expected, run the following command to install the
plugin locally.$pythonsetup.pydevelop