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

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

[Octave-bug-tracker] [bug #56937] BIST tests needed for interpreter form


From: Rik
Subject: [Octave-bug-tracker] [bug #56937] BIST tests needed for interpreter format command
Date: Mon, 23 Sep 2019 14:19:43 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko

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

                 Summary: BIST tests needed for interpreter format command 
                 Project: GNU Octave
            Submitted by: rik5
            Submitted on: Mon 23 Sep 2019 11:19:42 AM PDT
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Other
                  Status: Confirmed
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

The format command has many different styles (general, eng, bank, hex, rat,
etc.), combined with different options (short/long, compact/loose), combined
with different value types to display (real scalar, complex scalar, real
matrix, complex matrix), combined with other outside options such as
fixed_point_format().

Unfortunately, there are essentially no BIST tests and small changes can
introduce regressions as has already happened between versions 4.2 and 4.4
with respect to "format long".

It would be best if we had reasonable BIST tests so we could practice
test-driven development and not cause further problems while trying to fix the
ones that already exist.






    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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