Changes between Version 14 and Version 15 of PromotExplorerTest

Timestamp:

Jul 17, 2009, 10:47:43 AM (16 years ago)

Author:

mirschel

Comment:

--

PromotExplorerTest

@@ -3 +3 @@
 '''Setup A: ''' [[BR]]
 Model type: 'Logical Model'. [[BR]]
-Test to be applied: 1,4, 5, 6, 11, 12-15, 22-25, 26-27 [[BR]] 
+Test to be applied: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12-16, 17-21, 22-25, 26-27, 28, 29, 30 [[BR]] 
 Start ProMoT server and GUI -> load the logical library [source:/Promot/trunk/promot/kb/SignalTransd/structure/struct-ana-library.mdl]
 -> load the logical toymodel from tutorial [source:/Promot/trunk/promot/kb/SignalTransd/structure/toymodel_tutorial/LOAD_toymodel.mdl] 
@@ -10 +10 @@
 '''Setup B: ''' [[BR]]
 Model type: 'Dynamical Model'. [[BR]]
-Tests to be applied: None [[BR]]
+Tests to be applied: 2, 5, 8, 9, 10, 29[[BR]]
 Start ProMoT server and GUI -> load [source:/Promot/trunk/promot/kb/practical-bio/LOAD.mdl] which includes the library (reduced-library) for dynamic modeling 
 -> Open the Visual Explorer for the browser tree node 'dynamic-model' --> 'mapk_modules' --> 'mapkc' by right mouse click --> context menu --> Visual Explorer.
@@ -16 +16 @@
 '''Setup C: ''' [[BR]]
 Model type: 'SBML Model'. [[BR]]
-Tests to be applied: None [[BR]]
+Tests to be applied: 2, 5, 8, 9, 10, 29 [[BR]]
 Start ProMoT server and GUI -> import a biomodels.org model (e.g. BIOMD0000000001.xml) 
 -> Open the Visual Explorer for the browser tree node 'sbml-model' --> 'name of model' by right mouse click --> context menu --> Visual Explorer.
@@ -22 +22 @@
 '''Setup D: ''' [[BR]]
 Model type: 'Unknown Model'. [[BR]]
-Tests to be applied: None [[BR]]
+Tests to be applied: 2, 5, 8, 9, 10, 29 [[BR]]
 Start ProMoT server and GUI -> load [source:/Promot/trunk/promot/kb/practical/LOAD.mdl] which loads the 'tank' model -> Open the Visual Explorer for the browser tree node 'tank-plant' --> 'mc-tank-plant' by right mouse click --> context menu --> Visual Explorer.
 
 === JUnit Tests ===
 
- 1. Import node and edge attributes [[BR]] [source:/Promot/trunk/promot/src/gui/org/mpg/dcts/promot/viznav.data.io.AttributeReaderTest.java] [[BR]] [source:/Promot/trunk/promot/src/gui/org/mpg/dcts/promot/viznav.data.io.DelimitedTextReaderTest.java][[BR]] Check that two files (edge attributes, node attributes) are loaded properly. The attributes should be mapped to the existing nodes and edges in the graph correctly.
+ 1. Import node and edge attributes [[BR]] [source:/Promot/trunk/promot/src/gui/org/mpg/dcts/promot/viznav/data/io/AttributeReaderTest.java] [[BR]] [source:/Promot/trunk/promot/src/gui/org/mpg/dcts/promot/viznav/data/io/DelimitedTextReaderTest.java][[BR]] Check that two files (edge attributes, node attributes) are loaded properly. The attributes should be mapped to the existing nodes and edges in the graph correctly.
  
- 2. Load global scenarios [[BR]] [source:/Promot/trunk/promot/src/gui/org/mpg/dcts/promot/viznav/visual/VisualPropertyTest.java] [[BR]] Check that the global scenario file (.!PromotVizScenarios) is at the given location and calculators are loaded properly from the file.
+ 2. Load global scenarios [[BR]] [source:/Promot/trunk/promot/src/gui/org/mpg/dcts/promot/viznav/visual/VisualPropertyTest.java] [[BR]] Check that the global scenario file (.!PromotVizScenarios) is at the given location and calculators are loaded properly from the file. Test is independent of the model type.
 
  3. Scenarios: Logical Network Parser [[BR]] [source:/Promot/trunk/promot/src/gui/org/mpg/dcts/promot/viznav/data/logical/LogicalNetworkParserTest.java] [[BR]] Check that part of the logical network parser, especially parsing of DUMMY element and NOT element.
@@ -89 +89 @@
  28. Search for node/edge in network [[BR]] Search for the compound '!r2' (attribute == !PromotName, Case sensitive == on, Display options == Highlight, Navigation Options == Hierarchy Zoom), click button 'Search', compound '!r2' is emphasized by 'Global Highlight Node Color' (default red color) applied on the node border, display should zoom to compound '!r2', click button 'Clear' should remove the string input in the dialog and the highlight border color.  
 
- 29. Check model type [[BR]] Check the correct interpretation of the loaded model. [[BR]] Using Setup A, a logical model should be loaded, in the 'Statistics' dialog the model type should be 'Logical Model', default scenario should be 'Logical Network'. [[BR]] Using Setup B, a dynamical model should be loaded, in the 'Statistics' dialog the model type should be 'Dynamical Model', default scenario should be 'Visual Editor'. [[BR]] Using Setup C, a SBML model should be loaded, in the 'Statistics' dialog the model type should be 'SBML Model', default scenario should be 'SBML Model'. [[BR]] Using Setup D, a unknown model type should be loaded, in the 'Statistics' dialog the model type should be 'Unknown Model', default scenario should be 'Visual Editor'.
+ 29. Check model type [[BR]] Check the correct interpretation of the loaded model. Four cases:[[BR]] 
+   1. Using Setup A, a logical model should be loaded, in the 'Statistics' dialog the model type should be 'Logical Model', default scenario should be 'Logical Network'.
+   2. Using Setup B, a dynamical model should be loaded, in the 'Statistics' dialog the model type should be 'Dynamical Model', default scenario should be 'Visual Editor'. 
+   3. Using Setup C, a SBML model should be loaded, in the 'Statistics' dialog the model type should be 'SBML Model', default scenario should be 'SBML Model'.    
+   4. Using Setup D, a unknown model type should be loaded, in the 'Statistics' dialog the model type should be 'Unknown Model', default scenario should be 'Visual Editor'.
 
 === Not tested / not critical / trivial ===