Skip to main content

Testing Phase

After an admin approves an extension version for testing, that version enters the testing status. You can invite up to 5 testers (Free plan) or 20 testers (Pro plan) to provide feedback. An invitation does not make the testing version installable: installation always selects the extension's latest published version. For a published private extension, a tester invitation grants installation access to that published version.

How testing works​

  1. Admin approves the extension → status changes to testing
  2. You invite testers by Lumio username
  3. Testers provide feedback via the dashboard; if the extension already has a published version, they can install that published version
  4. When you're satisfied, you request publication

Inviting testers​

In the extension dashboard under Versions → {version} → Testing:

  1. Click Add tester
  2. Enter the tester's Lumio username
  3. Click Invite

The tester receives a notification. A store link can lead to a published extension, but it does not install the version in testing:

https://lumio.vision/dashboard/store/k8f2x-sports-scoreboard

Tester limits​

PlanMax testers per version
Free5
Pro20

Tester feedback​

Testers can submit feedback in the dashboard on the extension's testing page. Feedback is visible to the developer and the reviewing admin.

Feedback categories:

  • Bug report (extension crashes, incorrect behavior)
  • Visual issue (layout broken, text cut off)
  • Feature request
  • General comment

Testing badge​

Extensions in the testing phase show a "Beta" badge in the store if they are unlisted - so testers who find the link know the extension is not yet fully released.

Requesting publication​

When testing is complete and you're ready to publish:

  1. Open Versions → {version} → Testing
  2. Click Request publication
  3. The status changes to pending_publish
  4. An admin performs a final check and publishes the extension

Publication typically happens within 24 hours of the request.

Abandoning a testing version​

If you discover a significant bug during testing, you can deploy a new version and submit it for review without publishing the current testing version. The current testing version remains in testing status until you explicitly abandon it or publish it.

CLI: checking testing status​

lumio status
# Status: testing
# Testers: 3 active
# Feedback: 2 messages