ruby-clean-test 1.0.0-2 source package in Ubuntu

Changelog

ruby-clean-test (1.0.0-2) unstable; urgency=medium

  * Team upload.

  [ Debian Janitor ]
  * Use secure copyright file specification URI.
  * Bump debhelper from old 9 to 13.
  * Set debhelper-compat version in Build-Depends.
  * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
    Repository-Browse.
  * Update Vcs-* headers from URL redirect.
  * Use canonical URL in Vcs-Git.
  * Update watch file format version to 4.
  * Use secure URI in debian/watch.

  [ Daniel Leidert ]
  * d/control: Add Rules-Requires-Root field.
    (Standards-Version): Bump to 4.6.0.
    (Homepage): Update URL.
    (Depends): Remove interpreters and use ${ruby:Depends}.
  * d/rules: Use gem installation layout.
  * d/watch: Use gemwatch URL.
  * d/upstream/metadata: Add YAML header and Archive field.

 -- Daniel Leidert <email address hidden>  Sat, 13 Nov 2021 21:14:28 +0100

Upload details

Uploaded by:
Debian Ruby Extras Maintainers
Uploaded to:
Sid
Original maintainer:
Debian Ruby Extras Maintainers
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Jammy release universe misc

Builds

Jammy: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
ruby-clean-test_1.0.0-2.dsc 2.0 KiB 59a9b05b050a70d669dabe0ac22070dd3282679157926523d2ebe2896de9f5be
ruby-clean-test_1.0.0.orig.tar.gz 15.4 KiB 76e93311e4d032f5cbccea897d215c3647382e6d3d37c3d0766c3c789c7d7dbf
ruby-clean-test_1.0.0-2.debian.tar.xz 2.6 KiB 333d40758b5066616fc488191c77fa828f9a3a22c17fe3f9817267926411c0c5

Available diffs

No changes file available.

Binary packages built by this source

ruby-clean-test: Get unit tests readable and fluent

 This library is a set of small, simple tools to make your Test::Unit test cases
 easy to understand. This isn't a massive change in how you write tests, but
 simply some helpful things will make your tests easier to read.
 .
 The main problems this library solves are: understanding what part of a test
 method is setup, test, and evaluation; understanding what elements of a test
 are relevant to the test, and which are arbitrary placeholders; removing the
 requirement that your tests are method names.