Skip to content

KasaTapoClient Tests v1.0.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 15 Sep 06:55
· 47 commits to main since this release
KasaClient.ProcessorTests-v1.0.1
f4261f9

KasaTapoClient Tests

1.0.1

  • Rebuild the existing suite with CrestronHomeNUnit 1.2.1 so processor execution participates in the shared reservation used by the runner, Test Explorer, CLI and hardware CI.
  • Add the collection's Test Explorer workflow project for build, deployment, execution and optional temporary-instance cleanup. Independent library solutions can include it through an excluded local composite solution.
  • Device-sensitive live suites remain optional. Credentials and local settings are supplied privately and are not included in this package.
  • The processor package remains net472-only and appears in Configure's Utility category. This release contains GitHub assets only; it publishes no NuGet package or underlying library change.

Initial public processor test package, version 1.0.0. This is a test-package release; no library or production driver NuGet package is published.

  • 97 deterministic NUnit unit tests, plus seven opt-in live test placeholders. Device-specific configuration can expand the live cases.
  • Live tests support stable device selectors, discovery shared per run, state restoration and read-only T310/T315 hub temperature checks.

Install KasaClient.ProcessorTests.pkg, then add Utility → Neil Colvin → KasaTapoClient Tests in Crestron Home Configure. All processor test packages use the Utility category. The standalone Home tile runs automatic suites; the Windows runner provides discovery, selection and detailed results. Each package includes its own host; the NUnit self-test package is optional.

The .sources.json asset records the exact source revisions. The documentation ZIP includes license notices; SHA256SUMS.txt covers every other asset. Private settings, deployment credentials and live results are excluded. NUnit 4.6.1 is the official NuGet framework, not a private fork.

CI validates desktop tests and discovery from the packaged assembly. Processor runs are a separate hardware validation; the unit and configured live suites have passed during local processor testing. Live tests are never executed in CI.

Assets 6
Loading