use Perl

• Nice job. (Score:1)

  by jk2addict (4946) on 2007.11.06 10:30 (#58851) Homepage Journal

  This post is just to prove that people hate change.
  
  I've followed the email dev threads, and overall, the amount of improvements and work in 3.x is impressive. Nice job all.
  
  With that said, I totally hate the new Test Summary Report format and 'skipped'. The old way was much more readable imho. Maybe my eyes will retrain with time. Who knows.
  
  From an 80 col command window:
  
  OLD:

  t\pod_coverage............................skipped
          all skipped: set TEST_AUTHOR to enable this test
  t\pod_spelling............................skipped
          all skipped: set TEST_AUTHOR to enable this test
  t\pod_syntax..............................skipped
          all skipped: set TEST_AUTHOR to enable this test
   
  Failed Test                  Stat Wstat Total Fail  List of Failed
  ------------------------------------------------------------------------ -------
  t\catalyst\controller_rest.t  255 65280    15   24  4-15
  t\catalyst\live_rest_users.t    3   768    15   17  3 5 7 9-15
  t\catalyst\view_feed.t          1   256    76    1  40
  t\var\TestApp\t\01app.t       255 65280     2    3  1-2
  5 tests skipped.
  Failed 4/38 test scripts. 25/1774 subtests failed.
  Files=38, Tests=1774, 96 wallclock secs ( 0.00 cusr +  0.00 csys =  0.00 CPU)
  Failed 4/38 test programs. 25/1774 subtests failed.

  NEW:

  t/pod_coverage..............................skipped: set TEST_AUTHOR to enable t
  his test
  t/pod_spelling..............................skipped: set TEST_AUTHOR to enable t
  his test
  t/pod_syntax................................skipped: set TEST_AUTHOR to enable t
  his test
   
  Test Summary Report
  -------------------
  t/catalyst/controller_rest.t            (Wstat: 65280 Tests: 3 Failed: 0)
    Non-zero exit status: 255
    Parse errors: Bad plan.  You planned 15 tests but ran 3.
  t/catalyst/live_rest_users.t            (Wstat: 768 Tests: 8 Failed: 3)
    Failed test number(s):  3, 5, 7
    Non-zero exit status: 3
    Parse errors: Bad plan.  You planned 15 tests but ran 8.
  t/catalyst/view_feed.t                  (Wstat: 256 Tests: 76 Failed: 1)
    Failed test number(s):  40
    Non-zero exit status: 1
  t/var/TestApp/t/01app.t                 (Wstat: 65280 Tests: 1 Failed: 1)
    Failed test number(s):  1
    Non-zero exit status: 255
    Parse errors: Bad plan.  You planned 2 tests but ran 1.
  Files=38, Tests=1754, 96 wallclock secs ( 0.52 usr +  0.13 sys =  0.65 CPU)
  Result: FAIL

  Reply to This

  • Re: (Score:2)

    by Ovid (2709)

    Thanks. I'm glad you like what we did, with the exception of the output.

    Regarding the output, we do take requests :) Also, it's not too hard to write your own view, but we do want to make it even easier in the future.

    Out of curiosity, which Catalyst version is that? I'm having trouble finding it on CPAN and I want to see those parse errors.

    So far I find Catalyst [cpan.org]. That's just a short POD file :(

    There's also Catalyst::Runtime [cpan.org] which appears to be the correct Catalyst, but I can't tell.

    There's also
    • Re: (Score:1)

      by jk2addict (4946)

      Actually, that's output from the Mango tests (all in a state of no workie)...of which all Cat related tests are in t/catalyst/
      
      http://svn.mangoframework.com/CPAN/Mango/trunk/ [mangoframework.com]
      
      And yes, the current Catalyst is Catalyst::Runtime.
    • Re: (Score:1)

      by Aristotle (5147)

      Catalyst has been split into Catalyst-Runtime [cpan.org] (just the engine), Catalyst-Devel [cpan.org] (all the developer tools; has many more dependencies than the runtime alone) and Catalyst-Manual [cpan.org] (separated so it can be updated without necessitating a -Runtime/-Devel release).