Skip to content

The package concept in lisp-unit is confusing #55

Description

@jimka2001

I don't understand the package requirement in lisp-unit, it seems in violation of the philosophy of Common Lisp. Why is a package argument required for functions like run-tests ? Shouldn't the package come from the given symbol, ie from the test name? It seems the code tries and fails to allow something like the following, and I don't understand the benefit.

CL-USER> (lisp-unit:run-tests '(pack1:test1 pack2:test1) :pack3)

If my project defines many different packages, how can I test them all with a single call to run-tests? I.e., a call with will accumulate all the pass/fail/error events into one single report?

Looking at the code, it seems to me (correct me if I'm wrong), but a call to run-tests is only allowed to run a set of tests which are all in the same package. I don't see a benefit if this limitation.

What would make sense would be that the :package argument is only used when :all is given as the test-names argument, but in this case package should be a package designator or list thereof. This would allow me to call something like the following.

CL-USER> (lisp-unit:run-tests :all '(:pack1 :pack2 :pack3))

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions