octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #38776] Tests in private functions cannot be t


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #38776] Tests in private functions cannot be tested directly
Date: Fri, 19 Apr 2013 11:01:58 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:20.0) Gecko/20100101 Firefox/20.0 Iceape/2.17

URL:
  <http://savannah.gnu.org/bugs/?38776>

                 Summary: Tests in private functions cannot be tested directly
                 Project: GNU Octave
            Submitted by: philipnienhuis
            Submitted on: Fri 19 Apr 2013 01:01:56 PM CEST
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: Philip Nienhuis
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

See:
- bug #38755, 
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672756
- file ./scripts/miscellaneous/private/__xzip__.m,
-
https://mailman.cae.wisc.edu/pipermail/octave-maintainers/2013-April/033225.html,
and

Short summary: there's no way to run tests included in functions in ./private
subdirs.

For Octave that's not a problem per se, but for Debian it is.
But it would be good to be able to check proper operation of private functions
as well.

Possible solutions (in arbitrary order):
1- While running test script (e.g., scripts/testfun/runtests.m), temporarily
extend the PATH to the private subdir at hand and run all tests found there.
2- Move (rip out) tests from private functions to (?the most fitting?)
functions in the parent folder.
3- Design tests in functions in the parent folder such that private functions
are (implicitly) tested as well.
4- Comment out tests in private functions once correct operation has been
verified.

Any others?

Note that 1- (my preferred solution) may not directly help Debian, but IMO
that's not a first priority for Octave anyway (OTOH no reason to ignore
them).





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?38776>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]