/usr/lib/python3/dist-packages/lift-2.5.0.egg-info/PKG-INFO is in lift 2.5.0-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 | Metadata-Version: 1.1
Name: lift
Version: 2.5.0
Summary: High level test framework
Home-page: https://github.com/Malizor/lift
Author: Nicolas Delvaux
Author-email: nicolas.delvaux@arkena.com
License: GPL2+
Download-URL: https://github.com/Malizor/lift/tarball/2.5.0
Description: Lift Integration-Functional Testing - A meta test framework
===========================================================
[](https://travis-ci.org/Malizor/lift)
Usually, there is not much to discuss when writing unit tests.
They have to use the same programming language as the code they are testing
and most languages have a set of dedicated test frameworks that you may chose from.
However, functional and integration tests are more often a bunch of
scripts/executables written in different languages.
For example, you may prefer to use shell scripts to test a web-service
(eg. via `curl`) and a Python program to interact with Python modules.
And if C/Ruby/Perl/PHP/whatever is more suited to some of your test cases,
you want to use these languages too without having to write the full test suite with it.
Currently, most projects seem to have either multiple functional/integration
test suites (re-using different unit testing frameworks) or internal solutions
to group all the tests executable together in a more or less clean way.
Lift provides an integration/functional test platform which handles *executable*
tests easily and generically.
### Features
* Lift only deals with *executables* and their return code
→ A particular test can be written in the language that fit it the most
* Test declaration in a simple YAML syntax
→ No need to learn a programming language to integrate a test in a suite
* Easily declare a test as running locally or on a remote machine
* Remote tests: upload needed assets automatically and cleanup afterward
* Naturally organize a test suite in multiple sub-folders/sub-test suites
* Easily run a sub-test suite or specific tests from the command line
* Pass environment variables to tests
* Inheritance of remotes and environment across sub-test suites
→ For example, remotes can be defined in the top folder and used below
* Only one command to run all or specific tests: `lift`
* Export XUnit reports, for easy integration with Jenkins & friends
### Documentation
The `doc` folder contains man pages.
### Example
For a fully commented example of a lift test suite (which can also be seen as
a functional test suite for Lift itself), see the `example` folder.
### Installation
Use `sudo python3 setup.py install`
##### Dependencies
* Python 3 (>= 3.3)
* python3-yaml
* python3-paramiko
* python3-docutils (for man pages)
* python3-junit.xml
### Home page
https://github.com/Malizor/lift
### License
GNU General Public License (GPL) version 2+
Please refer to the COPYING file.
Keywords: test testing
Platform: UNKNOWN
Classifier: Development Status :: 5 - Production/Stable
Classifier: Intended Audience :: Developers
Classifier: Operating System :: Unix
Classifier: Programming Language :: Python :: 3
Classifier: Environment :: Console
|