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

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

[Octave-bug-tracker] [bug #55250] test suite severely overcounts "files


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #55250] test suite severely overcounts "files with no tests"
Date: Wed, 19 Dec 2018 19:08:48 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

URL:
  <https://savannah.gnu.org/bugs/?55250>

                 Summary: test suite severely overcounts "files with no tests"
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Wed 19 Dec 2018 04:08:46 PM PST
                Category: Test Suite
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

On the default branch, the test suite overcounts the number of .m files that
have no built-in tests. This is because it seems to be looking at .m files in
the 'test' directory now, where these were not considered before. This is a
regression from the stable branch.

For example, on a recent 'make check' on the stable branch (or Octave version
4.4.1), the end of the output reports


164 (of 821) .m files have no tests.


On the current default branch (01f1e70c80b6), 'make check' reports


367 (of 1041) .m files have no tests.


The number of .m files under the top-level 'test' directory is 192. 4 of these
are under a "private" directory, so that leaves 188. And these files do not
show up in the tail section of fntests.log on the stable branch, but all 188
files do show up in fntests.log on the default branch.




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55250>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

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