Package: purkinje
purkinjeTest runner for py.test test framework with web GUILive DemoBuild StatusBranchStatusdevmasterGetting Startedpurkinje is a browser application intended to run on a spare monitor. It shows results of automated
tests in realtime. Currently, the only supported test framework ispy.test.To use purkinje:Option 1: with DockerQuickstart using default configurationPull and start purkinje:docker run -ti -p15000:5000   --rm bbiskup/purkinje_dist:latestOpen the URLhttp://localhost:15000/in your browser.Customizing the configurationCreate a configuration filepurkinje.ymlwith the
following contents:global:logLevel:debugdebugMode:yesserverPort:5000serverHost:localhostPull and start purkinje:docker run -ti -p15000:5000  -v$PWD/docker/purkinje.yml:/code/purkinje.yml --rm bbiskup/purkinje_dist:latest purkinje -c purkinje.ymlOpen the URLhttp://localhost:15000/in your browser.Port 15000 is the port on which you access the purkinje web app with your browser;
this may have to be changed in case the port is already in usePort 5000 is the port inside the container; may not be changed.Option 2: without DockerCreate a virtual environment for purkinje and activate it:mkvirtualenv purkinje
workon purkinjeInstall purkinje:pip install purkinjeOptionally, create a configuration filepurkinje.ymlwith the
following contents:global:logLevel:debugdebugMode:yesserverPort:5000serverHost:localhostLaunch it:purkinje -f purkinje.ymlor, without configuration file:purkinjeOpen it in a browser:google-chrome http://localhost:5000/Prepare your Python/py.test project for reporting to purkinje. In your project’s virtualenv,
install the py.test plugin for purkinje:pip install pytest-purkinjeThis will automatically activate the plugin and test results will be sent to the
purkinje server. If you changed the host and/or port, specify them in your
project’spytest.ini:[pytest]addopts=--websocket_host myhost --websocket_port 40000If the settings should be incorrect, there will be a warning message but your
tests will execute nevertheless. You may add-pno:purkinjetopytest.inior as a command line argument topy.testto disable the purkinje plugin.Run your tests. The results should be visible in the browser:py.testAlternatively, you may runpurkinje_runnerin your project directory. It will
automatically detect changes the the sources and execute py.test:purkinje_runnerKnown LimitationsSecurity: There isno access restriction; for now, use only on the local machineAnyone can use the web applicationAnyone can send test results to the purkinje serverBy default, the server is running on localhost and not accessible from
other machines.Only a single test suiteIf you run multiple purkinje-enabled test suites simultaneously, test results
will get mixed up. This might change in a future version.System RequirementsPython 2.7.tested on Ubuntu 16.04needs a modern browser that supports WebSocketsPython development packages (python-devon Ubuntu) are required to build the dependencygevent.Supported Python versionsCurrently, only 2.7.x is supported. Python 3 support is blocked by the following packages:cssmininotifyx(which is blocking gevent_inotifyx)Supported Operating SystemsThe server part has only been tested on Ubuntu Linux 14.04 and 16.04 (64 bit).The web application should work on any operating system using a modern browser
(tested with Chrome 40-57 and Firefox 35-53).DevelopmentSource codeGitHub pageDevelopment environmentDockeranddocker-composerequired to develop purkinje.Installation instructions forDocker enginedocker-composeNote:docker-composeversion >= 1.6 is required because thedocker-compose*ymlfiles use syntax version 2.Apart from Docker, GNUmakeis required. All other development tools and
dependencies are provided by the Docker configuration.In the top-level directorypurkinje, run:makeThe development environment may be used either by running variousmakecommands based
ondocker.cmd, or interactively by running:make bashThe Docker image for distribution is built by the make targetbuild-docker-dist-img;
see.travis.yml.Versioningusessemantic versioningusesgit-flow git workflowChangeLogSome minor changes were omitted from this list. For details, see git log.Release 0.1.102017-10-28Experimental support for Python 3.5updated some dependendenciesRelease 0.1.92016-05-14Reduced size ofpurkinjepackage
- don’t add web assets cache
- remove some unnecessary JS resourcesConfigurable asset compressionUpdated most third-party Python libsUpdated some third-party JavaScript libsAdded cache control headerAdded warning about hanging Flask server withgeventwhenwatchdogpackage is installedmisc. minor fixesRelease 0.1.82015-06-28Changed demo server URL (HostEurope server)Upgraded py versionRemoved obsolete debug output of problematic JS package simple-statisticsPin version of simple-statistics to 0.9.0, as 0.9.2 has errorMiscellaneous fixes/improvements related to TravisShorter test function namesMiscellaneous code style improvementsSet github homepageRelease 0.1.72015-03-08Fix: Removed duplicate dependency (fixes Travis build)Syntax highlighting for YAML/INI fragments in README.rst
(thanks toMarc Abramowitz)Release 0.1.62015-03-08Fix: Added install_requires to setup.pyFix: Added missing requirements cssmin, pyamlRelease 0.1.52015-03-08Updated documentation with regard to new pytest-purkinje plugin parametersRelease 0.1.42015-03-07Fix: formatting in README.rstRelease 0.1.32015-03-07Fix: formatting in README.rstRelease 0.1.22015-03-07Optional configuration filelogLevel, debugMode, serverPort configurabledisabled desktop notificationsArial as fallback for Droid Sans font (the latter may not be available
on Windows)Release 0.1.12015-03-02Hide button for creation of dummy dataRelease 0.1.02015-03-02Basic functionality: ability to display running test suiterestricted to local network interface (no access restriction on
sending and viewing test results)Start of Development2014-12-11