This project provides a database of test results which can be used as part of
developer workflow to ensure/check things like:
* No commits without having had a test failure, test fixed cycle.
* No commits without new tests being added.
* What tests have failed since the last commit (to run just a subset).
* What tests are currently failing and need work.
Test results are inserted using subunit (and thus anything that can output
subunit or be converted into a subunit stream can be accepted).
Specifications for callback functions passed in to an API
If your code lets other people supply callback functions, it's important to
specify the function signature you expect, and check that functions support
that. Adding extra parameters later would break other peoples code unless
you're careful.
backcall provides a way of specifying the callback signature using a prototype
function.
Taint::Util wraps perl's internal routines for checking and setting
the taint flag and thus does not rely on regular expressions for
untainting or odd tricks involving eval and kill for checking
whether data is tainted, instead it checks and flips a flag on the
scalar in-place.
Cache::Memcached::Fast is a Perl client for memcached. Module core
is implemented in C and tries hard to minimize number of systemi
calls and to avoid any key/value copying for speed. As a result,
it has very low CPU consumption.
Parameterized testing in Python sucks. 'parameterized' fixes that. For
everything. Parameterized testing for nose, parameterized testing for py.test,
parameterized testing for unittest.
Version 4.1:
Protection agains buffer overflow and negative indexes in __getitem__ and __setitem__ for objc.varlist instances.
Fix incorrect metadata for +[NSEvent addLocalMonitorForEventsMatchingMask:handler:]
Fix incorrect and misleading error message in the exception that is raised when return a value from a block that should not return a value.
Issue 223: Fix hard crash when executing help(Cocoa)
Fetching the help for PyObjC framework wrappers isn’t very useful due to the sheer size of the output (4.5 million lines of output for help(Cocoa) at the moment), but shouldn’t cause a hard crash of the interpreter.
Issue 218: Explictly cause an ImportError when reloading `objc._objc`
Reloading the PyObjC core extension now raises an ImportError because this cannot work and used to raise a rather vague error.
Updated metadata for Xcode 9.2
Added missing `MAC_OS_X_VERSION_*` constants
Fix memory error in struct wrappers which resulted in a use-after-free error in the initializer for structs.
Add bindings for frameworks Security, SecurityFoundation and and SecurityInterface.
The bindings for the Security framework don’t expose a number of older APIs that were deprecated in macOS 10.7.
Add bindings to libdispatch.
These bindings require macOS 10.8 or later, libdispatch was available earlier but macOS 10.8 changed the API in such a way that wrapping became a lot easier.
pytest-asyncio is a library, written in Python, for testing asyncio code with
pytest.
asyncio code is usually written in the form of coroutines, which makes it
slightly more difficult to test using normal testing tools. pytest-asyncio
provides useful fixtures and markers to make testing easier.
Python 3.6 added async generators. Python 3.7 adds some more tools to make them
usable, like contextlib.asynccontextmanager. This library gives you all that
back to Python 3.5.
retry_decorator is a Python module that exposes a decorator that retries the
decorated function with exponential backoff.
This is yet another dependency for PR pkg/52941.
The deprecation library provides a deprecated decorator and a
fail_if_not_removed decorator for your tests. Together, the two enable the
automation of several things:
1. The docstring of a deprecated method gets the deprecation details appended to
the end of it. If you generate your API docs direct from your source, you don't
need to worry about writing your own notification. You also don't need to worry
about forgetting to write it. It's done for you.
2. Rather than having code live on forever because you only deprecated it but
never actually moved on from it, you can have your tests tell you when it's
time to remove the code. The @deprecated decorator can be told when it's time
to entirely remove the code, which causes @fail_if_not_removed to raise an
AssertionError, causing either your unittest or py.test tests to fail.
Clint is awesome. Crazy awesome. It supports colors, but detects if the session
is a TTY, so doesn't render the colors if you're piping stuff around.
Automagically.
Current Features:
* Little Documentation (bear with me for now)
* CLI Colors and Indents
* Extremely Simple + Powerful Column Printer
* Iterator-based Progress Bar
* Implicit Argument Handling
* Simple Support for Incoming Unix Pipes
* Application Directory management
Changes since 2.5.5:
Sat, Dec 2, 2018 - xdebug 2.6.0alpha1
+ Added features:
- Implemented issue #474: Added "memory" output to profiling files, to find out where memory is allocated.
- Implemented issue #575: Dump super globals contents to error log upon errors, just like when this would happen for stack traces.
- Implemented issue #964: Parse X-Forwarded-For for the first IP address when selecting the remote_connect_back host (Steve Easley).
- Implemented issue #990: Add DBGp: notifications for notices and warnings to be shown in IDEs.
- Implemented issue #1312: Implement extended_properties feature to remote debugging to support names and values with low ASCII values.
- Implemented issue #1323: Added xdebug.filename_format setting to configure the formatting of filenames when tracing.
- Implemented issue #1379: Added support for Unix domain sockets to xdebug.remote_host (Sara Golemon).
- Implemented issue #1380: Added xdebug_is_debugger_active() that returns true when debugger is connected.
- Implemented issue #1391: Added support for earlier stack frames through new argument for xdebug_call_* functions.
- Implemented issue #1420: Handle PHP 7.2's new methods for switch/case
- Implemented issue #1470: Added xdebug.remote_timeout to make connect timeout configurable.
- Implemented issue #1495: Make var_dump() also use the new xdebug.filename_format when formatting filenames.
+ Improvements:
- Implemented issue #847: Added support for "%s" specifier for xdebug.trace_output_name.
- Implemented issue #1384: Compile warning on Ubuntu 16.04 with GCC 5.4.x.
- Implemented issue #1401: Improved error message in case the connection breaks.
- Implemented issue #1430: Change DBGp tests to use TEST_PHP_EXECUTABLE instead of hard coded 'php'
- Implemented issue #1484: Use FD_CLOEXEC with debugging sockets to prevent FDs from leaking to forked processes (Chris Wright).
- Improve the foldexpr in xt.vim to fold lines correctly (Donie Leigh).
= Fixed bugs:
- Fixed issue #1272: property_get doesn't return @attributes for SimpleXMLElement.
- Fixed issue #1305: Property names with quotes can not be fetch while debugging.
- Fixed issue #1431: Fix "use after free" with in add_name_attribute_or_element.
- Fixed issue #1432: Fixed memory leak with xdebug_path_info_dtor.
- Fixed issue #1449: Debugging breaks with array element keys containing low-ASCII variables.
- Fixed issue #1471: Tracing crashes with return_assignments and ternairy operator.
- Fixed issue #1474: Crashes due to variable resolving/reading mechanism not taking care of temporary hash tables correctly (Nikita Popov, Derick).
- Fixed issue #1481: Fixed s390x and ppc64 builds (Remi Collet).
- Fixed issue #1486: Crash on ZEND_SWITCH_LONG / ZEND_SWITCH_STRING with more than 32 cases.
- Fixed issue #1496: Rewrite README.rst to be more clear on how to install and build Xdebug.
~ Changes:
- Fixed issue #1411: Use Error (Throwable) instead of fatal error when maximum nesting level is reached.
- Removed features:
- Implemented issue #1377: Drop support for PHP 5.5 and 5.6, only PHP 7 is now supported
pytest-relaxed provides 'relaxed' test discovery for pytest.
Has it ever felt strange to you that we put our tests in tests/, then name the
files test_foo.py, name the test classes TestFoo, and finally name the test
methods test_foo_bar? Especially when almost all of the code inside of tests/
is, well, tests?
This pytest plugin takes a page from the rest of Python, where you don't have
to explicitly note public module/class members, but only need to hint as to
which ones are private. By default, all files and objects pytest is told to
scan will be considered tests; to mark something as not-a-test, simply prefix
it with an underscore.
A tiny library to facilitate visitor implementation in Python (which are
slightly peculiar due to dynamic typing). In fact, it is so small, you may just
be better off copy and pasting the source straight into your project.
so it will show a stack dump of all threads running at the time. This is useful
when running tests under a continuous integration server or simply if you don't
know why the test suite hangs.
Note that while by default on POSIX systems py.test will continue to execute
the tests after a test has timed, out this is not always possible. Often the
only sure way to interrupt a hanging test is by terminating the entire process.
As this is a hard termination (os._exit()) it will result in no teardown, JUnit
XML output etc. But the plugin will ensure you will have the debugging output
on stderr nevertheless, which is the most important part at this stage.
Notes from py-unittest2:
There was a separate version of unittest2 for Python 3. This is no longer needed, but still exists on PyPI. This had the project name "unittest2py3k" but uses the same package name ("unittest2").
IDE for a programming language, last release 2005, no homepage.
I can't even find a good resource on the language ("while") this IDE
is for, and it is broken since there is no supported jdk in pkgsrc.
the failures and --ff to run all tests but the failures from the last run
first. For cleanup (usually not needed), a --clearcache option allows to
remove all cross-session cache contents ahead of a test run.
Ideally, tests reliably pass or fail, but sometimes test fixtures must rely on
components that aren’t 100% reliable. With flaky, instead of removing those
tests or marking them to @skip, they can be automatically retried.
local disk files in asyncio applications.
Ordinary local file IO is blocking, and cannot easily and portably made
asynchronous. This means doing file IO may interfere with asyncio
applications, which shouldn't block the executing thread. aiofiles helps with
this by introducing asynchronous versions of files that support delegating
operations to a separate thread pool.
uvloop and asyncio, combined with the power of async/await in Python 3.5,
makes it easier than ever to write high-performance networking code in Python.
uvloop makes asyncio fast. In fact, it is at least 2x faster than nodejs,
gevent, as well as any other Python asynchronous framework. The performance
of uvloop-based asyncio is close to that of Go programs.
