Skip to content

Conversation

@chrisveilleux
Copy link
Member

Description

The VoightKampff tests for this skill were producing false positives in the tests that check for stopping an expired timer. Added a timer.stopped-expired event that is emitted when any expired timer is stopped. The tests now check for this event rather than the existence of a beeping sound to determine if an expired timer was successfully stopped.

During testing of this PR, it was determined that several of the "stop" commands that have been passing should not be. These are words that are not included in the vocabulary of the Stop Skill (a.k.a. System Skill). They have been marked as "expected fail" temporarily.

This PR is dependent on Mycroft Core PR 3002.

Type of PR

If your PR fits more than one category, there is a high chance you should submit more than one PR. Please consider this carefully before opening the PR.

  • Bugfix
  • Feature implementation
  • Refactor of code (without functional changes)
  • Documentation improvements
  • Test improvements

Testing

Run the VK tests with a version of core that includes the changes in the aforementioned PR.

Documentation

Docstrings have been included in all the new testing code.

Copy link
Contributor

@krisgesling krisgesling left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah love it - given the Skill currently plays the beep sound we can be pretty confident that if the Skill doesn't think a timer has expired then it shouldn't be playing the beep anymore.

@chrisveilleux chrisveilleux force-pushed the bugfix/failing-vk-tests branch from 2f8a1a1 to 1c57bbc Compare September 28, 2021 18:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants