Saravanan666/pypi-org huggingface dataset:
Package: nose-colorxunit
Why?Why do I write this plugin for nose ,The reason is so
sample that the nose original report is so ugly, what’s the worse, not
friendly for tester, actually python tester.How?How to use this nose plugin: colorunit, Only tree steps you need to follow:Install colorunit:1.1) Install with pippip install nose-colorxunit1.2）Uninstall with pippip uninstall nose-colorxunit2.1) Install with sourceFirst, active your own python virtual environment if you have.Then on the terminal type:python setup.py build

python setup.py installIf you just want to install it as a super user or using sudo command, please think it again.2.2) Uninstall with sourceJust go to your own python virtual environment site-packages
directory, and find nose_colorxunit-..-py..egg, then delete it.Register colorunit [Optional]Now this is optional, just write the following code snippet into Any
one of your test files if you like, for example, test_demo.py.:import nose
from colorunit import ColorUnit
if __name__ == '__main__':
    nose.main(addplugins=[ColorUnit()])Run the test filesnosetests --with-colorunitNoteWithout –with-colorunit, the output will be the original report!Be sure that you are working in your own python virtual environmentConnectionsName: Lesus

Email: walkingnine@gmail.com          |

Blog: http://my.oschina.net/swuly302/blog (Chinese)If you have some good advice or idea, Welcome to communicate with me via email or be one of contributors!TODOAdding a decorator class or method for finding and showing these taken time over your expected taken time.Logging the output into specific fileIssuesOnly for Linux[Fixed v0.1.2];Only for python2., not supports python3[Fixed v0.2.0]Showing every test case taken time[Fixed v0.1.4]Why it needs to be registered again. For more informations, Please see How : Register colorunit section[Fixed v0.1.4]SnapshotOn Ubuntu:On Windows XP:Thanks!Vim 7.4stackeditnosecoloramaLICENSEAPACHE LICENSE VERSION 2.0Also see LICENSE file
Package: nose-congestion
Nose can report test execution time in its various output formats but it
doesn’t include thesetUportearDowntime, which can be substantial.Usagepip installnose-congestionnosetests--with-congestionOutputAfter all of the tests complete, a simple table will be printed:Location                                       Total    setUp tearDown
----------------------------------------------------------------------
module.tests.FastTests                         7.187    1.659    0.000
module.tests.SlowTests                         0.047    0.002    0.000

  Total  Location
----------------------------------------------------------------------
  0.104  module.tests.SlowTests.test_method
  0.009  module.tests.FastTests.test_methodRequirementsnosePython 2.6+, Python 3.3+
Package: nose-cover3
Version:0.1.0InstallationYou can installnose-cover3either via the Python Package Index (PyPI)
or from source.To install usingpip,:$ pip install nose-cover3To install usingeasy_install,:$ easy_install nose-cover3If you have downloaded a source tarball you can install it
by doing the following,:$ python setup.py build
# python setup.py install # as rootBug trackerIf you have any suggestions, bug reports or annoyances please report them
to our issue tracker athttp://github.com/ask/dispatch/issues/ContributingDevelopment ofnose-cover3happens at Github:http://github.com/ask/nosecover3You are highly encouraged to participate in the development. If you don’t
like Github (for some reason) you’re welcome to send regular patches.LicenseThis software is licensed under theLGPL License. See thelgpl.txtfile in the top distribution directory for the full license text.
Package: nose-cprof
A plugin to use cProfile to profilenosetests, rather than the
built-in Hotshot profiler.Profiling tests can help track down sources of performance issues in
code, especially if a synthetic test can be created to focus on the area
of concern.The output generated by this plugin can easily be browsed usingpstats_viewer, or any
other pstats-compatible viewer.Getting startedPrerequisitesThis is a plugin fornose,
so it’s useless without that installed.Installationpip installnose-cprofUsageThis plugin adds some new options tonosetests:--with-cprofile       Enable plugin cProfiler:  Use this plugin to run tests
                      using the cProfile profiler.  [NOSE_WITH_CPROFILE]
--cprofile-stats-file=FILE
                      Output file name; default "stats.dat"
--cprofile-stats-erase
                      Erase previously-collected profiling statistics before
                      run. Without this option, new profiling stats will be
                      merged with the prior contents of the output file.
Package: nosedbreport
Introductionnosedbreport exposes a single plugin that can front various backend databases to store
the result of a nose test execution. Having the results of your tests, whether they are part
of a continuous integration system or not, allows you to ask interesting questions about
your project such asWhat were the test suites that ran in the last five minutesWhat is the average time to run test case ‘x’What is the standard time to failure for test suite ‘y’and so on…These questions also allow you to build reporting, and monitoring tools based on automated
functional tests that you may be running against your development, staging or production
systems, such as heartbeat or availability pages.Installationwith easy_installsudo easy_install nosedbreportwith pipsudo pip install nosedbreportfrom source (git repository):hg clone http://github.com/alisaifee/nosedbreport
cd nosedbreport
python setup.py build
sudo python setup.py installUsageThe most basic use case is to report the results of a test run into a mysql database, which can be achieved by adding the following options to your nose execution:nosetests --dbreport-dbtype=mysql --dbreport-host=your.mysql.com\
 --dbreport-username=ali --dbreport-password=some-pass --dbreport-db=nosereportTo create the appropriate schema in your mysql database:nosetests --dbreport-dbtype=mysql --dbreport-host=your.mysql.com\
 --dbreport-username=root  --dbreport-password=your-root-pass\
 --dbreport-db=nosereport --dbreport-create-schemaFor detailed usage refer toread the docs
Package: nose-dehaze
nose-dehazeAnosetestsplugin to format and colorize test failure output for readability.Withoutdehaze:Withdehaze:Installationpipinstallnose-dehazeUsageLoad the plugin explicitly when calling nosetests:nosetests--dehazeor set the environment variable:exportNOSE_DEHAZE=1nosetestsSupported unittest assert methods:assertEqualassertNotEqualassertEqualsassertDictEqualassertSetEqualassertTupleEqualassertListEqualassertSequenceEqualassertIsassertIsNotassertIsNoneassertIsNotNoneassertIsInstanceassertNotIsInstanceassertTrueassertFalseMocks assert methods:assert_called_onceassert_called_once_withassert_not_calledassert_called_withassert_has_callsCurrently, diff colorization output can vary, especially for more complex assert comparisons such as
large, nested dicts. This is a side effect of the way dehaze calculates diffs by utilizing difflib
and passing in stringified expected/actual values.DevelopmentRefer toMakefilefor commands to test, autoformat, lint, typecheck, etc.pipinstall-rrequirements.txt# minimum to run codepipinstall-rrequirements-dev.txt# for autoformat, lint, type checking, debuggingpipinstall-rrequirements-test.txt# for running testsTesting# simply run testsmaketest# run tests with all supported python versionsmaketest-all
Package: nosedep
## Nosetest plugin for test dependencies.Normally tests should not depend on each other - and it should be avoided
as long as possible. Optimally each test should be able to run in isolation.However there might be rare cases or special circumstances where one would
want this. For example if having very slow integration tests where redoing what test
A did just to run test B would simply be too costly. Or temporarily while
testing or debugging. It’s also possible that one wants some test to run first
as ‘smoke tests’ such that the rest can be skipped if those tests fail.The current implementation allows marking tests with the@dependsdecorator
where it can be declared if the test needs to run before or after some
other specific test(s).There is also support for skipping tests based on the dependency results,
thus if test B depends on test A and test A fails then B will be skipped
with the reason that A failed.Nosedep also supports running the necessary dependencies for a single test,
thus if you specify to run only test B and test B depends on A; then A will
run before B to satisfy that dependency.Note that ‘before’ dependencies are treated as soft. A soft dependency will only
affect the test ordering, not force inclusion. For example if we have:def test_a:
  pass

@depends(before=test_a)
def test_b:
  passand run all tests they would run in the order b,a. If you specify to run only
either one of them only that test would run. However changing it to:@depends(after=test_b)
def test_a:
  pass

def test_b:
  passwould affect the case when you specify to run only test a, since it would have
to run test b first to specify the ‘after’ dependency since it’s a ‘hard’ dependency.Finally there is prioritization support. Each test can be given an integer priority
and the tests will run in order from lowest to highest. Dependencies take
precedence so in total the ordering will be:All tests with a priority lower or equal to the default that are not part of any
dependency chain ordered first by priority then by name.Dependency groups in order, while each dependency group is internally ordered
the same as point 1.All tests with priority higher than the default that are not part of any
dependency chain ordered first by priority then by name.Default priority if not specified is 50.Note: Currently no support for Python 2.6 and 3.2. Should work for 2.7 and 3.3+.## Info[![PyPI version](https://badge.fury.io/py/nosedep.svg)](https://pypi.python.org/pypi/nosedep)
[![Code Health](https://landscape.io/github/Zitrax/nose-dep/master/landscape.svg?style=flat)](https://landscape.io/github/Zitrax/nose-dep/master)
[![Build Status](https://travis-ci.org/Zitrax/nose-dep.svg?branch=master)](https://travis-ci.org/Zitrax/nose-dep)
[![Coverage Status](https://coveralls.io/repos/Zitrax/nose-dep/badge.svg?branch=master&service=github)](https://coveralls.io/github/Zitrax/nose-dep?branch=master)
Package: nose-descriptionfixer
This is a simple Nose plugin that forces nosetests to print the full test name in verbose mode, rather than just the docstring.For example, given the test fileexample.py:classMyTestCase(TestCase):deftest_without_docstring(self):passdeftest_with_docstring(self):"""This is my docstring"""passThis plugin changes the output ofnosetests-vexample.pyfrom:This is my docstring ... ok
test_without_docstring (mymodule.MyTestCase) ... okTo:test_with_docstring (mymodule.MyTestCase) ... ok
test_without_docstring (mymodule.MyTestCase) ... okInstall withpip installnose-description-fixer-plugin.
Package: nose-detecthttp
[not actively supported outside of internal Venmo usage]A nose and pytest plugin that can detect tests making external http calls.
With nose, it adds a single artificial failure with all the results:$ nosetests -v --with-detecthttp example.py
test_that_makes_request (example.ExampleTests) ... ok
test_with_no_request (example.ExampleTests) ... ok

======================================================================
FAIL: Tests made external http calls
----------------------------------------------------------------------
- example.ExampleTests:

    test_that_makes_request:
      GET http://example.com/


----------------------------------------------------------------------
Ran 2 tests in 0.063s

FAILED (failures=1)With pytest, failures are added to individual tests:$ pytest --with-detecthttp example.py
...

item = <TestCaseFunction 'test_that_makes_request'>

    def pytest_runtest_teardown(item):
        # Note unmocked interactions collected during runtest_call.
        # This is raised here so that pytest doesn't mark it as an internal error.

        report = item.config._detecthttp_reports.pop(item.nodeid, None)
        if item.config._detecthttp_enabled and report:
>           raise report
E           UnmockedRequestsDetected: detecthttp noticed the following requests during this test:
E                 GET http://example.com/

detecthttp/pytest.py:82: UnmockedRequestsDetected
...2 passed, 1 error in 0.35 secondsLocalhost is automatically ignored.
To ignore other hosts, use the–vcr-ignore-hostoption, which takes a comma-delimited list:$ nosetests -v --with-detecthttp --vcr-ignore-host=example.com example.py
test_that_makes_request (example.ExampleTests) ... ok
test_with_no_request (example.ExampleTests) ... ok

----------------------------------------------------------------------
Ran 2 tests in 0.110s

OKUnder the hood, this wraps every test in a separateVCR.py cassette.
Since VCR.py’s hooks are in the stdlib, this approach won’t detect requests made with clients like PycURL.History1.2.1Add Python 3 support1.1.0released 2018-12-18add pytest support1.0.0released 2018-09-12breaking: ignore host flag now accepts comma-separated values rather than being provided multiple times0.2.0released 2017-08-15add –vcr-ignore-host option to ignore custom hosts0.1.3released 2015-10-16python 3 support0.1.1released 2014-11-24initial release
Package: nose-django-querycount
Nose Django Querycount Plugin========================Counts queries for each test and shows result in the end in table. XML otputand other fancy stuff will be added later.Installation------------From the source repository:$ pip install git+git://github.com/dgladkov/nose-django-querycount.gitFrom PyPI:$ pip install nose-django-querycountUsage------------Currently only nose is supported, but native Django runner support is planned.Run like following:$ nosetests --with-querycountAlternatively, if you use [django-nose][], add it to your Django settingslike so:NOSE_ARGS = ['--with-querycount']NOSE_PLUGINS = ['nosequerycount.plugin.DjangoQueryCountPlugin',]Options------------$ nosetests --with-querycount --querycount-threshold=15Provides query count threshold for each test. If test run exceeds 15 queries,query count number will be red. Works only for terminal output and only ifyour terminal application supports coloring.Warning------------**This plugin sets DEBUG=True for tests, it can break your existing tests!**Django test runner sets DEBUG to False when when running test, but Djangosaves query log only when DEBUG mode is enabled.[django-nose]: https://github.com/jbalogh/django-nose
Package: nose-docstring-modifier
The project is available onGitHubInstallingYou can installnose-docstring-modifierplugin usingpip:$pipinstallnose-docstring-modifierUsingGiven the following test function, that usesnose-ittrplugin:@ittr(platforms=['P1','P2','P3'])@attr(section='MySection',type='functional+',module='MyModule',id=1)deftest_function(self):"""
    This is the original docstring
    """forplatforminself.platforms:ok_(True)running it withnosetestusingnose-docstring-modifierplugin:nosetests--with-docstring-modifier--prefix=id,section,platform--suffix=type--replace=('s','S')will print(1,MySection,P1)ThiSiStheoriginaldocString(functional+)...ok(1,MySection,P2)ThiSiStheoriginaldocString(functional+)...ok(1,MySection,P3)ThiSiStheoriginaldocString(functional+)...okNote that if you hardcode the platform on docstring, you cannot get dynamic output and you’ll get the same platform even when the test runs on three different platforms.FeaturesWorks with multiprocess plugin:nosetests--processes=10--process-restartworkerwith-docstring-modifier--prefix=idspreads test run among 10 processes, appendingidattribute to each test.History0.0.6 (2014-11-25)Added ability to display only first line of docstringChanged the way–replacecalled:–replace=(‘s’,’S’)0.0.5 (2014-11-24)HOTFIX - Fixed a bug that caused an error when running the plugin due to dependency with another upcoming plugin0.0.4 (2014-11-06)Code design changes0.0.3 (2014-11-05)Multiprocessing support0.0.2 (2014-11-04)Initial releaseAuthorsAuthors:Maroun MarounContributors:Tal Ben BasatNicole FrancoRoy KlingerSergey RagatskyVersion:0.0.6 of 26/11/2014
Package: nose-easy-init
A nose plugin, enabled by default, which executes a user-defined
initialization function prior to nose collecting or running any tests. The
user specifies the python module that contains the initialization function,main, in an environment variable.Use one of two environment variables to specify the module:NOSE_INIT_MODULE=app.tests.nose_initNOSE_INIT_PATH=/path/to/my/app/tests/nose_init.pyThen, run your nose tests as usual.Example initialization moduleLet’s assume that we’ve named our initialization modulenose_init.pyand
saved it in/path/to/my/app/tests/nose_init.py. That file must contain amainfunction. For example:"""
Initialization script which is imported when ``nosetests`` is run.
The main function will be executed before any other application code
is imported.
"""defmain():"""nose_easy_init will call this before each ``nosetests`` run."""setup_my_test_environment()setup_my_test_database()etc()Then, before runningnosetests, set one of two environment variables to
specify the module:NOSE_INIT_MODULE=app.tests.nose_initNOSE_INIT_PATH=/path/to/my/app/tests/nose_init.pyNote that if both the environment variables are defined, the filesystem path,NOSE_INIT_PATH, will take precedence overNOSE_INIT_MODULE.
Package: nose-enhanced-descriptions
A nose plugin to improve nose test description output.  This plugin deals with two problems in the default verbose nose output.   Finding out which test failed, and selectively rerunning tests.By default, running nosetests verbosely will describe each test with one ofAn id derived from the name and module of the testThe first line of the docstringthus:I have a docstring ... ok
test_with_blank_docstring (meta_tests.MetaTest) ... ok
I have a docstring ... ok
test_without_docstring (meta_tests.MetaTest) ... okIf you have multiple tests in different suites with the same or similar docstrings, and one of them fails, it can be difficult to find out which is which.The description derived from the name of the test is also frustrating.  The format of a command line argument to run a specific test in nose ismodule:TestClass.testmethod, yet the format of the description istestmethod (module.TestClass), meaning that the user must construct this argument by copying the various sections into the right place and replacing one of the dots with a colon.Usagenosetests--verbose--with-enhanced-descriptionsmeta_tests:MetaTest.test_docstring_leading_line
    (The first line was empty, but this is the line to use.) ... ok
meta_tests:MetaTest.test_with_blank_docstring ... ok
meta_tests:MetaTest.test_with_docstring
    (I have a docstring) ... ok
meta_tests:MetaTest.test_without_docstring ... okThe reader can see both the identifier (so that they know exactly which test fails), and the documentation (so that they know what it was supposed to do).  The test identifiers can alo now be copied and run,  e.g.nosetests meta_tests:MetaTest.test_without_docstring.Installationpip install nose_enhanced_descriptionsLicenceMIT
Package: nose_env_config
Plugin for configuration env variables with noseAvailable options:Set variables on nose run:--env-vars='var1=val1,var2=val2'Set file to read from:[env]
var1=val1
var2=val2and set path to it:--env-vars-file=/path/to/created/fileIf you don’t want to pass any flags you can go to ways:call your file.nose-envand put into directory you launch your
tests from;set environment variableNOSE_ENV_FILEwith path to your fileIf you configured your nosetests to read variables from files in one of
the ways, listed above, and you want to disable this option for a while
you can use--skip-env-vars-fileflag.Good luck!
Package: nose-exclude
Overviewnose-exclude is aNoseplugin that allows you to easily specify
directories to be excluded from testing.Exclude DirectoriesThe--exclude-dir=option is made available after installation of the
plugin. The option may be used multiple times to exclude multiple directories
from testing. The directory paths provided may be absolute or relative.Example:$ nosetests --exclude-dir=test_dirs/build \
    --exclude-dir=test_dirs/test_not_me test_dirs
....
----------------------------------------------------------------------
Ran 4 tests in 0.006s

OKThis example will exclude the directories test_dirs/build and
test_dirs/test_not_me from nosetests’ test searching.Using File-Based Exclusion ListThe--exclude-dir-file=option can be used to pass in a predefined
list of directories contained within a file.nose-excludeexpects each
directory to be excluded to be on its own line.Example:$ nosetests --exclude-dir-file=test_dirs/exclude_dirs.txt \
    test_dirs
....
----------------------------------------------------------------------
Ran 4 tests in 0.006s

OKwhereexclude_dirs.txtmight look like:test_dirs/build
# Start a line with a '#' to include
# Comments
test_dirs/test_not_meExcluding Specific Test Methods and ClassesTests can now be excluded by specifying their fully qualified test paths.
Tests can be excluded using either--exclude-testor--exclude-test-file.To exclude test methods:--exclude-test=module1.module2.TestClass.test_methodTo exclude test classes:--exclude-test=module1.module2.TestClassTo exclude test functions:--exclude-test=module1.module2.test_functionUsing Environment Variables--exclude-dir=and--exclude-test=can be set by the environment
variablesNOSE_EXCLUDE_DIRSandNOSE_EXCLUDE_TESTSrespectively.
Multiple exclude paths may be entered by separating them using a;. The
environment variableNOSE_EXCLUDE_DIRS_FILEwhen set to the path of a
file-based exclusion list functions as though it were passed in with--exclude-dir-file=.Nose Configuration Filesnose-excludeoptions can also be passed tonosetestsusing a.nosercornose.cfgfile. If you more than one directory are to be excluded
separate their values with newlines using the same configuration key:[nosetests]
exclude-dir=test_dirs/exclude_dirs
            test_dirs/more_excludesBugsPlease report all bugs (and patches) tohttps://github.com/kgrandis/nose-exclude/NOTE: The previous bitbucket repository is no longer actively maintained.
Package: nose_extra_tools
AboutExtra testing goodies fornose.tools.Adds anissues_warningsdecorator, where tests must issue one of the
expected warnings to pass (similar tonose.tools.raisesfor exceptions).If installed on Python < 2.7 backports the newunittest.TestCase.assert*methods, and converts them tonosestyle assertions (spelled in PEP 8
fashion, soassert_equalrather thanassertEqual):assert_greater/assert_less/assert_greater_equal/assert_less_equalassert_regexp_matches/assert_not_regexp_matchesassert_in/assert_not_inassert_is/assert_is_notassert_is_none/assert_is_not_noneassert_dict_contains_subsetandmore….InstallationTo installnose_extra_toolsrun:$ pip install nose_extra_toolsUsage examplesfrom nose_extra_tools import assert_in, issues_warnings

@issues_warnings(UserWarning, DeprecationWarning)
def test_issues_deprecation_warning():
    import warnings
    warnings.warn('This test passes')

@issues_warnings(Warning)
def test_forgot_to_issue_warning():
    pass

def test_backported_assert_in():
    assert_in(10, range(5))ContributeIf you find any bugs, or wish to propose new featuresplease let me know.If you’d like to contribute, simply forkthe repository, commit your changes
and send a pull request. Make sure you add yourself toAUTHORS.