closed Removal of one second when test launches

0 votes
asked Apr 16 in System Modelling by reg22017 (27 points)  
closed Apr 16 by reg22017

Due to my implementation of the timer in yakinda, as soon as test cases launch the clock, the timer manages to remove 1 second, and the test captures not 190 seconds but 189 seconds. Could it be related to my computer configuration, or it is more code issues?

base1 Succeeded!
base2 Succeeded!
optionCycle Succeeded!
checkSetStartTimeForWhite Succeeded!
checkSetStartTimeForBlack Succeeded!
checkSetBonusTime Succeeded!
checkSetMaxTime Succeeded!
checkSetStartPlayer Succeeded!
checkEffectSetStartPlayer Succeeded!

checkEffectSetStartTimeForWhite

  • MOD at 0s
  • MOD at 0s

    • Successful main display check #1: White initial time expected
    • Successful White player display check #2: 180 expected
  • White at 0s

    • Successful main display check #3: White initial time expected
    • Successful White player display check #4: 190 expected
  • MOD at 0s
  • MOD at 0s
  • MOD at 0s
  • MOD at 0s

    • Successful main display check #5: Ready to play expected
  • START at 0s

    • Successful main display check #6: White moves expected
    • Failed White player display check #7: expected "190" but found "189"

checkEffectSetStartTimeForBlack

  • MOD at 0s
  • MOD at 0s
  • MOD at 0s

    • Successful main display check #1: Black initial time expected
    • Successful Black player display check #2: 180 expected
  • White at 0s

    • Successful main display check #3: Black initial time expected
    • Successful Black player display check #4: 190 expected
  • MOD at 0s
  • MOD at 0s
  • MOD at 0s

    • Successful main display check #5: Ready to play expected
  • START at 0s
  • White at 0s

    • Successful beep check #6: true expected
    • Successful main display check #7: Black moves expected
    • Failed Black player display check #8: expected "190" but found "189"

checkEffectSetBonusTime

  • MOD at 0s
  • MOD at 0s
  • MOD at 0s
  • MOD at 0s

    • Successful main display check #1: Increment time expected
    • Successful White player display check #2: 10 expected
  • White at 0s

    • Successful main display check #3: Increment time expected
    • Successful White player display check #4: 15 expected
  • MOD at 0s
  • MOD at 0s

    • Successful main display check #5: Ready to play expected
  • START at 0s

    • Successful main display check #6: White moves expected
    • Failed White player display check #7: expected "180" but found "179"

checkResetInOptions Succeeded!
checkStartInGame Succeeded!

closed with the note: Done

1 Answer

0 votes
answered Apr 16 by dkmisu (1,321 points)  

I am pretty sure that this is a modeling issue. Your computer configuration does not play a part in this matter. I urge you to use the simulation feature of Yakindu to see exactly what goes on in your model when you start it.

...