Saravanan666/pypi-org huggingface dataset:
Package: nose-reportportal
agent-python-noseNose plugin for reporting test results of Nose to the 'Reportal Portal'.UsageConfigurationLaunchingCopyright NoticeChangesUsageInstallationTo install nose plugin execute next command in a terminal:pipinstallnose-reportportalConfigurationPrepare the config filerp.iniin root directory of testsTherp.inifile should have next mandatory fields:rp_uuid- value could be found in the User Profile sectionrp_project- name of project in Report Potalrp_endpoint- address of Report Portal Server, can be found in a environment variable "RP_ENDPOINT" after tests' runrp_launch- name of a launchrp_launch_description- description of a launchExample ofrp.ini:[base]
rp_uuid = fb586627-32be-47dd-93c1-678873458a5f
rp_endpoint = http://192.168.1.10:8080
rp_project = user_personal
rp_launch = AnyLaunchName {}
rp_launch_tags = Nose;Smoke
rp_launch_description = Smoke testYou need to add --rp-config-file to point to config file:--rp-config-filerp.iniIf you like to override some of parameters above from command line, or from CI environment based on your build, then pass--rp-launchto change launch name.--rp-modeto change mode of run report portal agent--rp-launch-descriptionto change description of a launch--ignore-loggerstto ignore external loggers and not send them in report portal. Specify which statements to filter. If the output is too verbose, use this option to filter out needless output.Example:filter=foo will capture statements issued ONLY to foo or foo.what.ever.sub  but not foobar or other logger. 
 Specify multiple loggers with comma: filter=foo,bar,baz.  
 If any logger name is prefixed with a minus, eg filter=-foo, it will be excluded rather than included.The following loggers are ignored
'nose'
'reportportal_client.service_async'
'reportportal_client.service' ,
'nose_reportportal.plugin'
'nose_reportportal.service'
'urllib3.connectionpool'
by default.LaunchingTo run test with Report Portal you must provide '--with-reportportal' flag:nosetests--with-reportportal--rp-config-filerp.iniCopyright NoticeCopyright Notice:https://github.com/reportportal/agent-python-nosetests#copyright-noticeLicensed under the Apache License Version 2.0, license (see the LICENSE file).Apache License Version 2.0:http://www.apache.org/licenses/LICENSE-2.0ChangesChanges in version 1.0.0updated version to support RP 5.0Changes in version 0.0.6 and 0.0.7freezed version of python client for RP 4.0Changes in version 0.0.5fixed problem with importing of LogCaptureChanges in version 0.0.4fixed bug with handling of skip status of a testadded argument to ignore loggersChanges in version 0.0.3a safe logs-sender  was added on a stop test phaseChanges in version 0.0.2Added updated capturing for output and logsAdded environment variable "RP_ENDPOINT" to exclude RP url from url-mockers if it is needed
Package: noserver-database
database:Simple package to store json data more easily !No server and simple use !fromnoserver_databaseimportDatabasedatabase=Database('database-name',debug=True)# init noserver_database | debug on True will show errors but no raise them# Create tabledatabase.create_table('table-name')# Get tabletable=database.get_table('table-name')# ortable=database>'table-name'# Add documentstable.insert_one({'message':'hello world','author':'armand@camponovo.xyz'})# Find documentsdocuments=table.find({'query':'value'})# search in all documents and return a list of documents that have the key 'query' at the value 'value'document=table.find_one({'query':'value'})# search in all documents and return the documents that have the key 'query' at the value 'value'all_docs=table.find({})# get all documents# Delete documents# for a simple doc:document.delete()# for a list of docs:forto_delete_documentindocuments:# to_delete_document.delete()...More documentation:database.data.Database(self, name: str, folder: str = 'auto', debug: bool = False, do_not_create=False):Methods:create_table(self, name: str)create a tableget_table(self, name: str)get a database.table.Table() object__gt__(self, name: str)get a database.table.Table() objectdatabase.table.Table(self, name: str, super_: Database):Methods:raw_json_data(self)get a list off all documents (in json) in the tableinsert_one(self, doc: dict)insert a document in the tablefind_one(self, doc: dict)return a database.document.Document() object that have the values of doc equal to the values of the returned documentfind(self, doc: dict)return a list of database.document.Document() object that have the values of doc equal to the values of the returned documentsdatabase.document.Document(self, data: dict, super_: Database, table_children: Table):Methods:__getitem__(self)return the item of the dict asked__del__(self)delete the document (this will return an error if you try document['item'] after that)
Package: nose_scenario
The ‘scenario’ plugin for ‘nose’ enables any test case to be
transformed into multiple copies of that test, each adapted for a
specific test scenario.The plugin will detect scenarios associated with one or more test
cases. It then generates a number of adapted copies of each test
case, one for each scenario, with the scenario data exposed to the
test case via attributes. Each adapted test case will then be run
separately by ‘nose’, and will be identified distinctly by the
scenario used.‘nose’ is a testing framework for Python code.
Package: nosescript
DescriptionA module for adding some QC-related features for python projects integrating
a bit of javascript.And it looks likeRequirementspython2.7libnspr4-devUsage# nose --with-jscriptunitWill scan packages and paths and match, as nose usually does, but also match
js files that correspond matchexp (test_*.js) and load them using a thin
integration api matching QUnit API. Results will be merged with the rest
of the test results.
Package: nose-seed-faker
nose-seed-fakerA nose plugin for seeding thefakerpackage based on test names.$ nosetests --with-seed-faker mytests/Faker is seeded at the beginning of each test based on the test name, so
each test that uses faker will use the same fake data between test runs,
regardless of test order.This relies on thebehaviorthat faker seeds a instance of random that is shared globally across
instances of the Faker class, so seedinganyinstance of Faker will
seedeveryinstance of Faker.For example, these two tests use faker to generate fake email addresses:importunittestfromfakerimportFakerfake=Faker()classTestEmail(unittest.TestCase):deftest_one(self):email=fake.email()print(email)deftest_two(self):email=fake.email()print(email)Since faker generates random email addresses, if we runtest_onemultiple times, we’ll use different emails for each test run:$ nosetests -v --nocapture tests.py:TestEmail.test_one tests.py:TestEmail.test_one
test_one (tests.TestEmail) ... opouros@hermistondeckow.com
ok
test_one (tests.TestEmail) ... sgrady@hotmail.com
ok

----------------------------------------------------------------------
Ran 2 tests in 0.001s

OKWhile this is good for increasing the surface area of emails we use in
our tests, it can cause flaky tests – a test could mysteriously fail,
but if you tried running it again to debug the failure, all of a sudden
it’s passing again!nose-seed-fakersolves this problem by seeding faker based on the
name of each test. Using the plugin, if you run the same test multiple
times, it’ll use the same email address:$ nosetests --with-seed-faker -v --nocapture tests.py:TestEmail.test_one tests.py:TestEmail.test_one
test_one (tests.TestEmail) ... mitchel07@yost.com
ok
test_one (tests.TestEmail) ... mitchel07@yost.com
ok

----------------------------------------------------------------------
Ran 2 tests in 0.001s

OKEach individual test will use a different email, so we still get a good
surface area of emails to use in our tests:$ nosetests --with-seed-faker -v --nocapture tests.py
test_one (tests.TestEmail) ... mitchel07@yost.com
ok
test_two (tests.TestEmail) ... kurt.bartell@yahoo.com
ok

----------------------------------------------------------------------
Ran 2 tests in 0.001s

OKInstallation$ pip install nose-seed-fakerWarningVersions0.5.2and lower of faker will seed therandommodule
globally.Version0.5.3fixesthis issue by seeding an instance of therandom.Randomclass, but at
the time of this writing, this fix hasn’t been released to PyPI yet.Until version0.5.3is released on PyPI, you can install it like so:$ pip install git+http://github.com/joke2k/faker.git@dabf922af72783ebd9d163611ab0f4f307156443#egg=fake-factory==0.5.3History0.1.2released 2015-06-30initial release
Package: nose-sfd
$ nosetests --with-sfdThis is an update of the NoseDjango v0.6 which is incredibly fast than the
new releases. This plugin will work with all the versions of Django.The aim of this fork is to keep the speed of the tests execution time
and provide a simple way to test Django applications with nose.Original authors:Victor Ng <crankycoder@gmail.com>Jason PellerinCHANGELOGv0.4Support for Django 1.7v0.3Fix support for South migrations on Postgres.v0.2Add support for South migrations.v0.1Initial release.
Package: nose-skipreq
This is a simple nose plugin which acts like the SkipTest plugin for Google’s
RequestError exception.Testing against live Google APIs–other than being a bad idea to begin
with–often results in random RequestError responses from Google. We may not
want these exceptions to cause test failures as they are transient and may be
handled gracefully by other parts of the system. To that end,nose-skipreqwas created.When runningnosetestswith the--skip-reqflag, all tests which raise
RequestError will be marked SKIP instead of FAIL. That’s it!
Package: nose-sphinx-doc
=============NoseSphinxDoc=============------------Introduction------------Nose plugin that will generate sphinx-formatted test documentation.With this nose plugin you can easily automate generation of sphinx documentationfor your tests. NoseSphinxDoc will create set of .rst files with proper references to tests,reflecting structure of your modules.------------Installation------------::pip install --upgrade "git+git://github.com/Fiedzia/NoseSphinxDoc.git#egg=Fiedzia"-----Usage-----Basically::nosetests --sphinx-doc --sphinx-doc-dir=/path/to/sphinx/doc/subdirectoryFor example, if you have your existing sphinx documentation in ./docs directory,actuall call will look like this::nosetests --sphinx-doc --sphinx-doc-dir=./docs/testsThis will create ./docs/tests directory, containing generated documentation.In order to link generated documentation you will need to reference./doc/tests/index.rst file somewhere in your documentation.Top level index.rst is a good place to do that.NoseSphinxDoc does not require test to actually be run, its should happily work withcollect-only plugin, so you can run nose to document all tests quickly,and then run it again to execute only chosen subset.If you use ``--sphinx-doc-graph`` option, a graph will be created,with a simple drawing of your tests structure. This requires ``sphinx.ext.graphviz``to be added to sphinx extension list.If it works for you, please let me know, i'd like to hear that i'v made something useful.---------Debugging---------If something doesn't work:* Make sure that nose runs succesfully without any plugins. If nosewill fail (you will see a failure information in nose output)then so will everything else and you will have to fix this problem first.If you are using several plugins, turn them on one by one,to find the culprit.* Look at ``PYTHONPATH``. You may need to set it properly for noseand for sphinx, as they both will need to look at python code the same way.Forcing them to do so is sometimes tricky, and nose can communicate errorsreally poorly.* If everything still fails, go to NoseSphinxDoc github page and create an issue,providing all details and minimal code that lead to an error.
Package: nose-sqlcapture
SQLCapture nose pluginCapture SQL queries being generated from a nosetests runInstallationDo`pip installnose-sqlcapture`in your project.  Your project should already have`nosetests`and`sqlalchemy`installed.Usage`nosetests [other options]--with-sqlcapture--sqlcapture-filename=sql.log--sqlcapture-format=json`sqlcapture-filename the output file. Default: /tmp/sqlcapture.logsqlcapture-format the format of the log file, either json or plain.  Default: plainFormatsPlain (plain)Output in plain-text form that’s meant for human consumption.  The output is of the following format:test1
test2
SQL1
---
test1
test3
SQL2
---
...JSON (json)Ouptut the queries and their corresponding tests in json format:{
    SQL1: [test1, test2],
    SQL2: [test1, test3],
    ...
}
Package: nose-summary-report
summary-reportA very basicnoseplugin providing a per-module tests status final report.Example output forpelican-pluginstests:----------------------------------------------------------------------
Summary:
         top-module | success | error   | failure
   -------------------------------------------------
    collate_content |       8 |       0 |       0
      disqus_static |       0 |       1 |       0
   filetime_from_hg |       0 |       1 |       0
         gzip_cache |       3 |       1 |       1
      i18n_subsites |       8 |       0 |       1
      image_process |       1 |       4 |       1
        jpeg_reader |       0 |       2 |       0
         libravatar |       0 |       1 |       0
        liquid_tags |       0 |       7 |       0
    more_categories |       3 |       0 |       0
    multi_neighbors |       0 |       1 |       0
  org_python_reader |       0 |       1 |       0
                pdf |       0 |       1 |       0
pelican_unity_webgl |       0 |       1 |       0
               nose |       0 |       4 |       0
         post_stats |       0 |       2 |       0
      reddit_poster |       0 |       1 |       0
      similar_posts |       0 |       1 |       0
   simple_footnotes |       1 |       0 |       1
            summary |       4 |       0 |       0
        thumbnailer |       0 |       1 |       0
----------------------------------------------------------------------
Ran 66 tests in 10.188s

FAILED (SKIP=9, errors=29, failures=4)Usagepip install nose-summary-report
nosetests --with-summary-reportYou can choose other ways to aggregate the tests status:nosetests --with-summary-report --summary-report-on class
nosetests --with-summary-report --summary-report-on module-pathDevelopmentReleasing a new versionWith a valid~/.pypirc:edit version insetup.pypython setup.py sdisttwine upload dist/*git tag $version && git push && git push --tags
Package: nosetalisker
A nose plugin that outputs one cProfile stat dump to a file, for each test.Installpip install nose-taliskerFormat of the file name is:module-name.class-name.test-name.elapsed-milli-seconds.timestamp.profFor example:zamboni.apps.files.tests.test_views.TestFileViewer.test_view_access_reviewed.001448ms.2011-06-09T01:50:34.323206.prof
zamboni.apps.files.tests.test_views.TestFileViewer.test_view_access_reviewed.001577ms.2011-06-09T01:56:51.694283.profOptionsprof_path: the destination directory to write to. If not given a temporary
one will be created for you. If you provide a directory, it must exist.Usagenosetests –with-talisker –prof-path=/tmp/outputThis module is designed to be used by talisker to consume and view the profile
results. The format is deliberately based upon the runprofileserver from the
command extensions module, with the same option naming.License: BSD
Author: Andy McKay,andym@mozilla.com
Package: nose-tap
nose-tap is a reporting plugin for nose that outputsTest Anything Protocol (TAP)data.
TAP is a line based test protocol for recording test data in a standard way.Follow development onGitHub.
Developer documentation is onRead the Docs.ReleasesVersion 3.0, Released February 10, 2020Drop support for Python 2.Version 2.0, Released December 26, 2019Drop Python 2.6 support.Version 1.9, Released June 19, 2016Initial release as stand-alone plugin.
The version number aligns with tappy.
Package: nose-terse-output
Really terse output from your nose tests. Just the bare essentials.Nose-terse-output is inspired bynose-machineout. It’s a reporter plugin to nose that doesn’t produce any output if a nose test run is successful, and only produce one line per error in a format that is easily parseable by editors, like VIM.Nose’s error messages are really hard for tools, like text editors, to parse in order to navigate to the location of the error. nose-terse-output takes that output and parses it to produce one line of information per failed test. That line has the format:<path>:<line>:<errormessage>That’s a whole lot easier for a text editor to parse.nose-terse-output accomplishes this by starting at the bottom of the call stack for the error, and walk upwards until it finds the first location that looks interesting.By default, the first stack frame that comes from the same basepath as the current directory and that doesn’t match ‘python’ or ‘venv’ will be selected as the location of the failing test.You can change the patterns of paths to ignore when walking the stack with the–terse-ignoreargument. You can use–terse-ignoreseveral times. You can also tell nose-terse-output that it’s ok to consider non local directories by using the–terse-outside-localargument.Default output from a failing test run:$nosetests--with-terseoutpath/to/test.py:123:testname:'foo'!='bar'To get a compact print out of the stack as well:$nosetests--with-terseout--terse-stackTo supply your own directories you’d like to ignore:$nosetests--with-terseout--terse-ignore="venv"--terse-ignore="helpers"To consider non-local directories:$nosetests--with-terseout--terse-outside-localInstall with:$pipinstallnose-terse-output
Package: nose-test-sets
Installation$ pip installnose-test-setsUsageTo define your set of common tests, create aTestSetBuilder, and useadd_testto add tests. Each test should accept the same name of
arguments. Say you define some tests for an adder in the moduleadder_test_set:from nose_test_sets import TestSetBuilder

test_set_builder = TestSetBuilder()
test = test_set_builder.add_test

@test
def adding_zero_to_zero_returns_zero(adder):
    assert adder.add(0, 0) == 0

@test
def adding_one_to_two_returns_three(adder):
    assert adder.add(1, 2) == 3

create = test_set_builder.createTo run the tests against a specific implementation, you create a set of
tests using thecreatefunction that we defined above:import adder_test_set

def _run_test_with_standard_adder(test_func):
    adder = StandardAdder()
    return test_func(adder)

StandardAdderTests = adder_test_set.create(
    "StandardAdderTests",
    _run_test_with_standard_adder
)The first argument tocreateshould be the name of the concrete test
set. The second argument is a function that can run each of the test
functions. In the example above, to run the tests inStandardAdderTests, nose-test-sets ends up calling_run_test_with_standard_adder(adding_zero_to_zero_returns_zero)and_run_test_with_standard_adder(adding_one_to_two_returns_three).
Package: nosetests-json-extended
Creates json logging output for python nosetests unittest framework.The generated output can be used by theatom-nosetestsplugin, which adds
python unit testing capability to theAtomeditor.This plugin is tested with python 2.7.8 and python 3.4.2.This plugin is tested withvirtualenv.InstallFirst install the package:pip install nosetests-json-extendedIt is also possible to install the development version:git clone git@github.com:thschenk/nosetests-json-extended.git
pip install nosetests-json-extendedUsageNormal usage:nosetests --with-json-extendedThis will automatically generate a filenosetests.jsonin the current working
directory.For python3, replacenosetestswithnosetests3, or use the following form:python3 -m nose --with-json-extended
Package: nosetests-json-extended-parallel
=======================nosetests-json-extended-parallel=======================I forked the original project because I need the bug fix for multiprocessing test. (no permission to create new branch from original project).. _original_project: https://github.com/thschenk/nosetests-json-extendedCreates json logging output for python nosetests unittest framework.The generated output can be used by the atom-nosetests_ plugin, which addspython unit testing capability to the Atom_ editor.* This plugin is tested with python 2.7.8 and python 3.4.2.* This plugin is tested with virtualenv_... _atom-nosetests: https://github.com/thschenk/atom-nosetests.. _Atom: https://atom.io.. _virtualenv: https://virtualenv.pypa.io/en/latest/Install-------First install the package:::pip install nosetests-json-extended-parallelIt is also possible to install the development version:::git clone git@github.com:ruivapps/nosetests-json-extended-parallel.gitpip install nosetests-json-extended-parallelUsage-----Normal usage:::nosetests --with-json-extended-parallelThis will automatically generate a file ``nosetests.json`` in the current workingdirectory.For python3, replace ``nosetests`` with ``nosetests3``, or use the following form:::python3 -m nose --with-json-extended-parallel
Package: nose-timelimit
nose-timelimitis a nose plugin that allows you automatically skip tests that are too slow.It requires at least one run with the whole suite to register the timings. If a test fails timings
are not registered for it (thus it will never get skipped).InstallationJust runpip installnose-timelimitoreasy_installnose-timelimit.Options--with-timelimit- Just activates the plugin (will only register timing data).--timelimit=X- Runs only the tests that had previously ran underXseconds. Implies--with-timelimit.--timelimit-silent- Don’t print the duration for each test.RequirementsKnown to work withnose 1.3, it may work with nose as old as0.10- try it.ExampleOn first run:And on second run:
Package: nose-timing
A simple plugin that combines test times and test setup times and writes the
output to JSON files. I ripped most of this out of nose-congestion:https://github.com/acdha/nose-congestionAnd added in a few bits for my own needs.This is a work in progress to do what I want and not much more at this point.UsageTo install:pip install nose-timingWhen running your tests add:--with-timingTo get your timing to run. By default it will write to your current directory
two files,setup.jsonandtests.json. To alter where it writes to:--output-directory=/tmp