← Back to team overview

sikuli-driver team mailing list archive

[Bug 966818] [NEW] Green indication for failed Unit test

 

Public bug reported:

Sikuli version X-1.0rc3
Windows7 64bit. 

When I'm runing this very basic sikuli script in the Sikuli IDE I'm
getting green bar on the right in UnitTest panel:

def setUp(self):
#    popup("setup")    
    pass

def tearDown(self):
#    popup("tear down") 
    pass

def testOne(self):
    popup("in one")
    assert not exists(Pattern("1332886672074.png").similar(0.50))
    assert exists(Pattern("1332886672074.png").similar(0.50))
#    assert not exists(Pattern("1332886672074.png").similar(0.90))

I believe that this bar should be red to visualize a problem.

Also note as per attaches screenshot it says Errors: 1, Failures: 0 and
further down it shows one failure. Should this tab be called Errors
instead of Failures?

thanks

** Affects: sikuli
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/966818

Title:
  Green indication for failed Unit test

Status in Sikuli:
  New

Bug description:
  Sikuli version X-1.0rc3
  Windows7 64bit. 

  When I'm runing this very basic sikuli script in the Sikuli IDE I'm
  getting green bar on the right in UnitTest panel:

  def setUp(self):
  #    popup("setup")    
      pass

  def tearDown(self):
  #    popup("tear down") 
      pass

  def testOne(self):
      popup("in one")
      assert not exists(Pattern("1332886672074.png").similar(0.50))
      assert exists(Pattern("1332886672074.png").similar(0.50))
  #    assert not exists(Pattern("1332886672074.png").similar(0.90))

  I believe that this bar should be red to visualize a problem.

  Also note as per attaches screenshot it says Errors: 1, Failures: 0
  and further down it shows one failure. Should this tab be called
  Errors instead of Failures?

  thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/966818/+subscriptions


Follow ups

References