Package: oejskit
jskit contains infrastructure and in particular apy.testplugin to
enable running tests for JavaScript code inside browsers directly
using py.test as the test driver. Running inside the browsers comes
with some speed cost, on the other hand it means for example the code
is tested against the real-world DOM implementations.The approach also enables to write integration tests such that the
JavaScript code is tested against server-side Python code mocked as
necessary. Any server-side framework that can already be exposed
through WSGI (or for which a subset of WSGI can be written to
accommodate the jskit own needs) can play along.jskit has also some support to run JavaScript tests fromunittest.pybased
test suites.jskit also contains code to help modularizing JavaScript code
which can be used to describe and track dependencies dynamically
during development and that can help resolving them statically when
deploying/packaging.Known supported browsers are Firefox, Internet Explorer >=7, and
WebKit browsers.jskit now supports both py.test 2.0 and late py.test 1.x.jskit requires Python 2.6 or 2.7. It also usesMochiKit- of
which it ships a version within itself for convenience - for its own
working though in does not imposes its usage on tested code.jskit was initially developed byOpen EndAB and is released under the MIT license.rest of the docs…Europython 2009 talk with examplesThe project repository lives athttp://bitbucket.org/pedronis/js-infrastructure/Discussions and feedback should go to py-dev at codespeak.netChangelog0.9.0make reusing one tab/window and the corresponding browser test
object for all tests using the same setup in a session the default,
this is enforced when using py.test 2.0 which collects all tests
firstpy.test 2.0 is now supported!py.test 1.x still works as welldisplay during the test runs a list of links on the upper right
corner of the pages to jump to the outcome sections corresponding to the
JavaScript test files or python modulesvarious internal cleanups and simplificationssome light refreshing and editing of the docsfix the looking up of jstests_setup values to consider the chain of
conftest.py correctlyMochiKit usage is really an implementation detail, switch to by
default in tests importing it with__export__=false, which means
the name MochiKit alone is defined in the global (window) namespace,
use in a jstests_setup:class jstests_setup:
    MochiKit__export__ = Trueto get the old behavior.0.8.9optionally delegate to the serverSide how the baseurl from which tests will be served should look like, useful when doing proxying  for functional testing abuse of oejskitchange packaging to just offer a source tar file, so that makes it easier to packagerequires Python 2.6 or 2.70.8.8improved code to check for the presence of browsers which is used to skip
tests, this means that listing non-present browsers in browser specs
should not provoke problemsworkaround to bug in FF3.5 triggered by the global var leak detection code,
no leak detection with FF3.5 :(0.8.7flexibleuser-defined-name=commandlinecontrol over browser names
forbrowser.py serverwith documentationdocument the glue to standard library unittest.pybetter error reporting when a browser cannot be starteduse json module included in Python >=2.6, simplejson otherwisemove the py.test plugin into the oejskit package, expose it through a pytest11 setuptools entry pointfix own-tests-only issues and warnings with py.test 1.1.x0.8.6fixes for py.test 1.0 final compatibilityexperimental glue to standard library unittest.py (no docs yet)