Ticket #697 (new bug)

Opened 6 years ago

Last modified 3 years ago

Parrot::Test "language_output_is" fails in installed parrot.

Reported by: coke Owned by:
Priority: normal Milestone:
Component: install Version: 1.2.0
Severity: medium Keywords:
Cc: jkeenan Language:
Patch status: Platform:

Description

In  partcl, any of the perl based tests are failing:

$ prove t/cmd_cd.t
[17:47:47] t/cmd_cd.t .. 1/3
#   Failed test 'cd too many args'
#   at t/cmd_cd.t line 17.
#          got: ''
#     expected: 'wrong # args: should be "cd ?dirName?"
# '
# '/usr/local/lib/parrot/1.2.0/tools/parrot  ........../tcl.pbc t/cmd_cd_1.tcl' failed with exit code -1

Looks like the path to parrot is wrong (This is on feather), and the path to tcl.pbc is wrong, assuming those ...'s are literal.

Change History

  Changed 6 years ago by coke

  • lang set to tcl

  Changed 5 years ago by pmichaud

  • component changed from none to install

  Changed 5 years ago by coke

  • lang tcl deleted
  • keywords tcl blocker removed

Are any language authors blocking on trying to use these testing methods? Should we just not install them or remove them entirely?

(partcl doesn't need them anymore)

follow-up: ↓ 5   Changed 5 years ago by coke

I haven't heard anyone speaking up for these testing methods; I vote for removing them

in reply to: ↑ 4   Changed 3 years ago by jkeenan

  • cc jkeenan added

Replying to coke:

I haven't heard anyone speaking up for these testing methods; I vote for removing them

From perldoc lib/Parrot/Test.pm:

    "language_output_is($language, $code, $expected,
    $description)"
    "language_error_output_is($language, $code, $expected,
    $description)"
        Runs a language test and passes the test if a string
        comparison of the output with the expected result is
        true. For "language_error_output_is()", the exit
        code also has to be non-zero.

    "language_output_like($language, $code, $expected,
    $description)"
    "language_error_output_like($language, $code, $expected,
    $description)"
        Runs a language test and passes the test if the
        output matches the expected result. For
        "language_error_output_like()", the exit code also
        has to be non-zero.

    "language_output_isnt($language, $code, $expected,
    $description)"
    "language_error_output_isnt($language, $code, $expected,
    $description)"
        Runs a language test and passes the test if a string
        comparison of the output with the unexpected result
        is false. For "language_error_output_isnt()", the
        exit code also has to be non-zero.

Are those the functions we were considering removing from this module? Do we still want to do that?

Thank you very much.

kid51

Note: See TracTickets for help on using tickets.