-
-
Notifications
You must be signed in to change notification settings - Fork 36
Reduce boilerplate testing code for single vibrator devices #403
Copy link
Copy link
Closed
Labels
good first bugGood bug to take if you want to start contributing to the projectGood bug to take if you want to start contributing to the projecthelp wantedBugs qDot doesn't wanna doBugs qDot doesn't wanna dolibraryIssues that span all parts of the library (usually code style related)Issues that span all parts of the library (usually code style related)testingTest/QA related issuesTest/QA related issueswontfix
Description
Metadata
Metadata
Assignees
Labels
good first bugGood bug to take if you want to start contributing to the projectGood bug to take if you want to start contributing to the projecthelp wantedBugs qDot doesn't wanna doBugs qDot doesn't wanna dolibraryIssues that span all parts of the library (usually code style related)Issues that span all parts of the library (usually code style related)testingTest/QA related issuesTest/QA related issueswontfix
Changes in #397 reduced the overall amount of test boilerplate quite a bit. However, there are still quite a few cases of repeated code for single vibrator devices that could probably be moved into some sort of base class that generates test cases.