Menu

#119 Some testing cleanups

Backlog
open
nobody
None
nobody
2022-07-11
2017-12-30
Ulf Lorenz
No

Leftovers from [#98]:

  • Utilities/ProgramOptions: One could add some tests that explicitly check that command-line arguments and configuration files work. After all, that is the main point of the test. Requires extension of the test script. Test and functionality has been dropped.
  • Testing of operators is cumbersome. To check that two operators (or Liouvillians or so) are identical, you apply both to a random test state and compare the output. This could have some utility functions to shorten the tests. By the way, you could also apply them to a unit density, which gives the matrix representation of the operator.
  • The time-independent operator primitives could have explicit tests that ensure that the spectral ranges are valid by comparing them to spectra obtained from diagonalizing. Currently, the test repeats the code too much.
  • TransformationOperator1D::setTransformation() is not tested explicitly; the usual code paths all go through the non-empty constructor that already gets the transformation.

Related

Tickets: #98

Discussion

  • Ulf Lorenz

    Ulf Lorenz - 2018-02-10
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,3 +1,4 @@
     Leftovers from [#98]:
    
     * Utilities/ProgramOptions: One could add some tests that explicitly check that command-line arguments and configuration files work. After all, that is the main point of the test. Requires extension of the test script.
    +* Testing of operators is cumbersome. To check that two operator primitives (or Liouvillians or so) are identical, you apply both to a random test state and compare the output. This could have some utility functions to shorten the tests.
    
     

    Related

    Tickets: #98

  • Ulf Lorenz

    Ulf Lorenz - 2019-01-25
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -2,3 +2,4 @@
    
     * Utilities/ProgramOptions: One could add some tests that explicitly check that command-line arguments and configuration files work. After all, that is the main point of the test. Requires extension of the test script.
     * Testing of operators is cumbersome. To check that two operator primitives (or Liouvillians or so) are identical, you apply both to a random test state and compare the output. This could have some utility functions to shorten the tests.
    +* The time-independent operator primitives could have explicit tests that ensure that the spectral ranges are valid by comparing them to spectra obtained from diagonalizing. Currently, the test repeats the code too much.
    
     
  • Ulf Lorenz

    Ulf Lorenz - 2019-09-02
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,5 +1,5 @@
     Leftovers from [#98]:
    
     * Utilities/ProgramOptions: One could add some tests that explicitly check that command-line arguments and configuration files work. After all, that is the main point of the test. Requires extension of the test script.
    -* Testing of operators is cumbersome. To check that two operator primitives (or Liouvillians or so) are identical, you apply both to a random test state and compare the output. This could have some utility functions to shorten the tests.
    +* Testing of operators is cumbersome. To check that two operators (or Liouvillians or so) are identical, you apply both to a random test state and compare the output. This could have some utility functions to shorten the tests. By the way, you could also apply them to a unit density, which gives the matrix representation of the operator.
     * The time-independent operator primitives could have explicit tests that ensure that the spectral ranges are valid by comparing them to spectra obtained from diagonalizing. Currently, the test repeats the code too much.
    
     

    Related

    Tickets: #98

  • Ulf Lorenz

    Ulf Lorenz - 2020-05-21
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,5 +1,5 @@
     Leftovers from [#98]:
    
    -* Utilities/ProgramOptions: One could add some tests that explicitly check that command-line arguments and configuration files work. After all, that is the main point of the test. Requires extension of the test script.
    +* <s>Utilities/ProgramOptions: One could add some tests that explicitly check that command-line arguments and configuration files work. After all, that is the main point of the test. Requires extension of the test script.</s> Test and functionality has been dropped.
     * Testing of operators is cumbersome. To check that two operators (or Liouvillians or so) are identical, you apply both to a random test state and compare the output. This could have some utility functions to shorten the tests. By the way, you could also apply them to a unit density, which gives the matrix representation of the operator.
     * The time-independent operator primitives could have explicit tests that ensure that the spectral ranges are valid by comparing them to spectra obtained from diagonalizing. Currently, the test repeats the code too much.
    
     

    Related

    Tickets: #98

  • Ulf Lorenz

    Ulf Lorenz - 2022-07-11
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -3,3 +3,4 @@
     * <s>Utilities/ProgramOptions: One could add some tests that explicitly check that command-line arguments and configuration files work. After all, that is the main point of the test. Requires extension of the test script.</s> Test and functionality has been dropped.
     * Testing of operators is cumbersome. To check that two operators (or Liouvillians or so) are identical, you apply both to a random test state and compare the output. This could have some utility functions to shorten the tests. By the way, you could also apply them to a unit density, which gives the matrix representation of the operator.
     * The time-independent operator primitives could have explicit tests that ensure that the spectral ranges are valid by comparing them to spectra obtained from diagonalizing. Currently, the test repeats the code too much.
    +* TransformationOperator1D::setTransformation() is not tested explicitly; the usual code paths all go through the non-empty constructor that already gets the transformation.
    
     

Log in to post a comment.