Create unit tests for each backend
Closed, ResolvedPublic


Following T3855, it is time to create unit tests to cover the features implemented in the backends. It will allow to verify if new versions of the programming languages are compatible with their backends.

In this task let's list the required tests to be implemented. If you have some idea to new tests, please write in comments so I can add in the task description.

Some tests to be implemented:

  • Test the run of simple command (command in one line);
  • Test the run of more complex command (more than one line);
  • Test simple variable definition;
  • Test matrix or vector variable definition;
  • Test error message after send wrong command;
  • Test import modules;
  • Test tab completion;
  • Test information request from backend (via needsAdditionalInformation signal)
  • Test plots, if they are supports
  • Test syntax help
  • Test help request
  • Test loading of saved projects - open a project, execute all commands and check the outputs. Test with and without "auto evaluation" option enabled.

Please, feel free to create new subtasks for each implementation.

asemke updated the task description. (Show Details)Apr 27 2018, 3:21 PM

After D13550(54f93b4b949e6b8e8222776f4681eb4bba3aa147) we can use Cantor without specify QT_PLUGIN_PATH.
But for tests it's not true, so for running tests we need use QT_PLUGIN_PATH.

sirgienko updated the task description. (Show Details)Apr 12 2019, 8:46 AM
sirgienko closed this task as Resolved.May 10 2019, 4:55 PM

In this moment, this task is done: only Qalculate and Kalgebra haven't tests at all (but this backends almost not supported), and lua have only few tests (but lua don't work correctly with command queue, so without solving this, adding more tests is pointless).