Ubuntu
lift package

lift 2.5.0-1 source package in Ubuntu

Changelog

lift (2.5.0-1) unstable; urgency=medium

  * New upstream release
  * Bump standards version to 3.9.8 (no change required)
  * Improve debian/copyright to please Lintian
  * Simplify the packaging: use Pybuild
  * Make the build reproducible (set the build date in manpages)
  * Bump the debian/watch version to 4 (no change required)
  * Bump the compat version to 10 (no change required)

 -- Nicolas Delvaux <email address hidden>  Sun, 25 Sep 2016 17:31:54 +0200

Upload details

Uploaded by:
Nicolas Delvaux
Uploaded to:
Sid
Original maintainer:
Nicolas Delvaux
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Focal release universe misc
Bionic release universe misc

Builds

Zesty: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
lift_2.5.0-1.dsc 1.7 KiB f5e4236eb99a9129d20dd4936b8029f4e23fc4a2810468a8af3ae3a4e7497bec
lift_2.5.0.orig.tar.xz 21.4 KiB 7e7f16652e5d5403d57eab08ef6cc5c690f79ef0ce4b75a3fd742199e710383a
lift_2.5.0-1.debian.tar.xz 4.6 KiB 4e8289c047ce9f7d20a713d402b061209faa0da0a725a59c4325afa3a155e894

No changes file available.

Binary packages built by this source

lift: Integration and functional testing framework

 Lift provides an integration/functional test platform which handles executable
 tests easily and generically.
 .
  * 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