Switch branches/tags
Nothing to show
Commits on Jun 30, 2015
  1. Added colour to backtraces

    The first line in the backtrace that starts with ./ is highlighted.
    This draws the eye to what is hopefully the most important line in the
    committed Jun 30, 2015
  2. .gitignore

    committed Jun 30, 2015
Commits on Jan 27, 2012
  1. Version 1.0.3.pre opened

    Updated doc/whitestone.markdown to reflect changes to Ft
    committed Jan 27, 2012
  2. Version 1.0.2 -- improved Ft implementation and testing

    * Improved the implementation and testing of float equality (Ft).
      There is a backwards-incompatible change in that Ft no longer
      accepts an epsilon argument. If Ft doesn't work for you with
      the built-in value (1e-13) then it's probably a bug in this
      library. Theoretically, this should be version 2.0.0, but that
      seems silly and I don't think anyone will be affected. Sorry
      if you are.
    committed Jan 27, 2012
Commits on Jan 5, 2012
Commits on Jan 2, 2012
  1. Updated gemspec with correct Ruby dependency

    Whitestone doesn't work on 1.8.6. Requires 1.8.7 or greater.
    committed Jan 2, 2012
Commits on Jan 1, 2012
  1. VERSION 1.0.1

    * Corrected mistake in README.txt
    * Introduced History.txt
    committed Jan 1, 2012
  2. Small doc change.

    committed Jan 1, 2012
  3. Added title to README.txt

    committed Jan 1, 2012
  4. 'pkg' >> .gitignore

    committed Jan 1, 2012
  5. Renamed project from 'attest' to 'whitestone'.

    Contents of all relevant files changed.  Relevant files renamed.
    committed Jan 1, 2012
  6. Deactivated failing Float test

    The test { Ft! 0, 0.00000000000124, 1e-25 } used to work (I think) but
    doesn't now (changed to 1.9.3).  I'm not sure what we really should
    expect here and it's not important enough to worry about.
    committed Jan 1, 2012
  7. Removed failing "insulation" tests

    It was expected that certain things done inside an insulated test
    (D!) would be invisible outside of that environment: class and
    constant definitions. This was expected to be false for 1.8 but true
    for 1.9. As of 1.9.3, it no longer appears to be true.
    This is not an important feature for me, so I'm happy to remove the
    failing tests and any mention of that "feature" in the documentation.
    committed Jan 1, 2012
  8. Introduced Bundler to build gem

     * etc/attest.gemspec -> attest.gemspec
     * etc/ no longer needed
    committed Jan 1, 2012
  9. Test tinkering

      * Floating point "numbers near zero" -- one of them doesn't work
        at the moment; needs investigation.
      * Cache ruby version for the version-specific tests D18 and D19.
    committed Jan 1, 2012
Commits on Dec 22, 2010
  1. More informative output for Float comparisons

     * Includes the ratio
    committed Dec 22, 2010
  2. Changes to float comparison again

     * Use difference if either value is zero (because there's no scale)
     * Use ratio otherwise (because scale is important)
     * Tests for tiny and huge numbers
    committed Dec 22, 2010
  3. File matching; float comparison

     * Better matching of exact filenames when selecting test files
     * Important correction to float comparison: Ft 1.1e-16, 0 used to fail
     * Small bugfix
    committed Dec 22, 2010
Commits on Jul 26, 2010
  1. README.txt reinvigorated

    And pithy quote copied to doc/attest.markdown.
    committed Jul 26, 2010
Commits on Jul 25, 2010
  1. Mt removes colour codes from strings before checking

    * Mt method removes colour codes from string before testing match with
      regular expression.
    * Documentation reflects this.
    * Tests reflect this.
    * Removed time() method and all calls to it from bin/attest.
    * Attest.time -> Attest.record_execution_time (use less common method
    That last bullet point raises an interesting thought: it was motivated
    by a name clash with the nascent 'debuglog' library.  But _why_ was
    Attest.time being loaded into the top-level namespace anyway?  What
    other pollution is happening?  We only want methods like D, T, Eq, ...
    committed Jul 23, 2010
Commits on Jul 18, 2010
  1. Backtrace filtering (and more) refactoring

    * Moved backtrace filtering _and_ file and line number hunting to new
      class BacktraceProcessor.  report_failure and report_uncaught_exception
      are now much slimmer and better factored.
    * Lines in backtrace are processed to be relative paths if possible.
      I've found this to be necessary in Ruby 1.9, but it may be something
      askew in my computer setup.
    * When reporting an error, greater care is taken to get the line number
      correct for the code output.  If a function exists in the same file as
      the assertion, and that function triggers the error, then before this
      commit it would be the _function_ that is shown in the code, not the
    committed Jul 18, 2010
  2. test/insulation.rb: updated for Ruby 1.9

    * classes and constants defined in an insulated test are not accessible
      outside the test (due to change in operation of instance_eval in 1.9).
    * tests run differently in 1.8 and 1.9 and give appropriate messages
      for each
    * methods in this class: D18 and D19 for version-sensitive test
      descriptions; hopefully migrate this functionality to core attest soon.
    committed Jul 18, 2010
  3. Doc -> extra difference from Dfect

    etc/at: run project version of attest, not a gem
    etc/gems-to-install: list of gems I should have installed for running
    committed Jul 18, 2010
Commits on Jul 17, 2010
  1. Test suite now passes in Ruby 1.8 and Ruby 1.9

    * There was a problem in 1.9: instance_eval can't take a lambda
      (  Custom assertions need to use 'proc'
      when specifying the :run code (lambda works in 1.8 but not 1.9;
      'proc' works in both).
    * Documentation changed to use proc instead of lambda.
    * CustomTestContext#initialize was using define_method that is
      implemented in the 'extensions' gem, which we're not using for
      Attest, but which was indirectly loaded.  Rewritten so it's
      not dependent on anything.
    * Some old bits of commented-out code removed.
    * All traces of 'dev-utils/debug' removed -- getting ready for 1.0!
    committed Jul 17, 2010
Commits on Jul 16, 2010
  1. Stats, -f, D! doc and test

    * @stats[:pass] no longer incremented when an assertion-less test runs
    * --filter and --full-backtrace can now apply to -f <file> as well
    * some doc updates, especially clarifying use and effect of D!
    * test/insulate.rb to explore and document the effects of D! on classes,
      modules, methods and instance variables
    * etc/extra_tests/{raise,stop}.rb -- looking into why Attest.stop doesn't
    committed Jul 16, 2010
Commits on Jul 15, 2010
  1. Documentation and presentation improvements

    * some improvements to bin/attest -h
    * many improvements to documentation, including syntax highlighting
    * lib/attest/include.rb: fix (rather important) typo
    * output.rb: very minor code improvement
    committed Jul 15, 2010
Commits on Jul 14, 2010
  1. Performance-measuring code - temporary

    * time() { ... }
    * Performane in running rgeom tests is poor; trying to determine why
      * Main bottleneck is all the external requires in rgeom.rb
    committed Jul 14, 2010
  2. Fixed 'Fl' failure display problem

    * Also added Fl examples to etc/extra_tests/output_examples.rb
    committed Jul 14, 2010
Commits on Jul 13, 2010
  1. --full-backtrace option to suppress filtering of backtraces

    * bin/attest: --full-backtrace option to suppress filtering of backtraces
    * lib/attest.rb, lib/attest/output.rb: support above feaure, and improve
      clarity of Output#filter_backtrace code, and ensure that assertion
      specification errors always filter the backtrace (as originally intended
      but broken in recent commit)
    * Updated documentation regarding this change
    committed Jul 13, 2010
  2. Uses "Col" for all colour output

    * This means String is no longer modified to provide methods like
      :yellow and :bold.  (It's not good for a testing library to change
      core classes; the changes could conflict with the code being tested.)
    committed Jul 13, 2010
  3. bin/attest -f <file> adjusts library path

    This was an inconsistency between `attest` and `attest -f`.
    Also updated details in etc/attest.gemspec
    committed Jul 13, 2010
Commits on Jul 12, 2010
  1. Select which test(s) you want to run; '-' for blank tests

    * bin/attest: --filter PATTERN option added, to select certain
      (top-level) tests to run
    * lib/attest.rb: implement test selection via :filter option to
      {run} method
    * tests that don't contain any assertions now have an output of '-',
      as intended in commit 16ff818
    * improved some colour and vertical spacing in output
    * fixed: attest -s will correctly run the test files separately
    * README.textile was out of date and has been cut down to size.
    * Removed examples from attest runner: it's a gimmick and perhaps
      better put into a document.
    * added better images to {attest.markdown} and text accomanying them;
      these are stored in the repository.
    * fixed failing tests from last commit (to do with sharing blocks);
      I'm now not 100% sure they're testing what they're supposed to.
    committed Jul 12, 2010