parameters: (self)
docstring: Ideally you should have several levels of tests.  At the lowest level
      tests should exercise the functionality of the logic with different inputs
      (both valid and invalid).  At higher levels your tests should emulate the
      way the user would interact with your code and confirm that it still works
      the way you intended.
      One of the most important features of the tests is that it should alert other
      developers when their changes will have an impact on the behavior of your
      module.  For example, if a developer removes a feature that you depend on,
      your test should break so they know that the feature is needed.
docstring_summary: Ideally you should have several levels of tests.  At the lowest level
      tests should exercise the functionality of the logic with different inputs
      (both valid and invalid).  At higher levels your tests should emulate the
      way the user would interact with your code and confirm that it still works
      the way you intended.
      One of the most important features of the tests is that it should alert other
      developers when their changes will have an impact on the behavior of your
      module.  For example, if a developer removes a feature that you depend on,
      your test should break so they know that the feature is needed.
docstring_tokens: Ideally you should have several levels of tests . At the lowest level tests should exercise the functionality of the logic with different inputs ( both valid and invalid ) . At higher levels your tests should emulate the way the user would interact with your code and confirm that it still works the way you intended . One of the most important features of the tests is that it should alert other developers when their changes will have an impact on the behavior of your module . For example if a developer removes a feature that you depend on your test should break so they know that the feature is needed .
function: def test_DataProbe1(self):
      """ Ideally you should have several levels of tests.  At the lowest level
      tests should exercise the functionality of the logic with different inputs
      (both valid and invalid).  At higher levels your tests should emulate the
      way the user would interact with your code and confirm that it still works
      the way you intended.
      One of the most important features of the tests is that it should alert other
      developers when their changes will have an impact on the behavior of your
      module.  For example, if a developer removes a feature that you depend on,
      your test should break so they know that the feature is needed.
      """
  
      self.delayDisplay("Starting the test")
  
      #
      # first, get some data
      #
      import SampleData
      SampleData.downloadFromURL(
        nodeNames='FA',
        fileNames='FA.nrrd',
        uris='http://slicer.kitware.com/midas3/download?items=5767',
        checksums='SHA256:12d17fba4f2e1f1a843f0757366f28c3f3e1a8bb38836f0de2a32bb1cd476560')
      self.delayDisplay('Finished with download and loading')
  
      self.widget = DataProbeInfoWidget()
      self.widget.frame.show()
  
      self.delayDisplay('Test passed!')
function_tokens: def test_DataProbe1 ( self ) : self . delayDisplay ( "Starting the test" ) # # first, get some data # import SampleData SampleData . downloadFromURL ( nodeNames = 'FA' , fileNames = 'FA.nrrd' , uris = 'http://slicer.kitware.com/midas3/download?items=5767' , checksums = 'SHA256:12d17fba4f2e1f1a843f0757366f28c3f3e1a8bb38836f0de2a32bb1cd476560' ) self . delayDisplay ( 'Finished with download and loading' ) self . widget = DataProbeInfoWidget ( ) self . widget . frame . show ( ) self . delayDisplay ( 'Test passed!' )