Ticket #1452 (closed enhancement: fixed)

Opened 2 years ago

Last modified 2 years ago

Refactor analysis test cases

Reported by: nicklas Owned by: nicklas
Priority: major Milestone: BASE 2.15
Component: test Version:
Keywords: Cc:

Description

It is currently a bit cumbersome to create test cases for analysis plug-ins because each test case must setup it's own experiment and import data to it and then remove everything after the test. It would be useful to have a utility class that sets up an experiment with some data, then all sorts of analysis tests can be done on that experiment. The experiment and data should not be removed until after all tests are completed.

Change History

comment:1 Changed 2 years ago by nicklas

  • Status changed from new to assigned
  • Owner changed from everyone to nicklas

comment:2 Changed 2 years ago by nicklas

(In [5228]) References #1452: Refactor analysis test cases

Added TestAnalysisUtil? that is supposed to setup a generic experiment and some other info. Changed tests for the following to use it:

  • Base1PluginExecuter
  • Basic tests for the core api
  • Intensity calculator plug-in
  • Lowess normalization
  • Median ratio normalization
  • Web services

The BioAssaySetExporter? tests have not yet been updated. It should be split into TestBaseFileExporterImporter? and TestBfsExporterImporter? tests.

comment:3 Changed 2 years ago by nicklas

(In [5230]) References #1452: Refactor analysis test cases

Fixed the BASEfile exporter tests. As it turned out there is no test for the importer, so I'll add a new ticket to create test for the importer.

comment:4 Changed 2 years ago by nicklas

(In [5231]) References #1452: Refactor analysis test cases

Removed unused code from TestBaseFileExporterImporter?.

comment:5 Changed 2 years ago by nicklas

  • Status changed from assigned to closed
  • Resolution set to fixed

(In [5233]) Fixes #1452: Refactor analysis test cases References #1451: Implement BFS importer for spot data

The BFS exporter/importer test case is now moved to a separate class.

Note: See TracTickets for help on using tickets.