This repository was archived by the owner on Jul 9, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 376
This repository was archived by the owner on Jul 9, 2025. It is now read-only.
Compare new luis model vs current production (batch testing) #3252
Copy link
Copy link
Closed
Labels
BacklogBacklog items - not in current milestoneBacklog items - not in current milestoneBot ServicesRequired for internal Azure reporting. Do not delete. Do not change color.Required for internal Azure reporting. Do not delete. Do not change color.ExemptFromDailyDRIReportUX DesignNeed UX DesignNeed UX Designcustomer-replied-toRequired for internal reporting. Do not delete.Required for internal reporting. Do not delete.customer-reportedRequired for internal Azure reporting. Do not delete.Required for internal Azure reporting. Do not delete.feature-requestA request for new functionality or an enhancement to an existing one.A request for new functionality or an enhancement to an existing one.
Description
Describe the solution you'd like
Compare a new Luis model in Composer vs Luis model in production
Luis has a batch testing feature which allows to check if your newly added utterances will not negatively affect existing intent recognition.
It would be great to have the ability to run batch testing from Composer to see upfront how changes made to User Input will influence the intent recognition results, compared to the current Luis model used in production. When implementing this type of feature, it should be possible to run batch testing in Composer before publishing updates to the bot in Azure.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
BacklogBacklog items - not in current milestoneBacklog items - not in current milestoneBot ServicesRequired for internal Azure reporting. Do not delete. Do not change color.Required for internal Azure reporting. Do not delete. Do not change color.ExemptFromDailyDRIReportUX DesignNeed UX DesignNeed UX Designcustomer-replied-toRequired for internal reporting. Do not delete.Required for internal reporting. Do not delete.customer-reportedRequired for internal Azure reporting. Do not delete.Required for internal Azure reporting. Do not delete.feature-requestA request for new functionality or an enhancement to an existing one.A request for new functionality or an enhancement to an existing one.