should not be able to save a utility without assets

should be able to successfully add and remove assets to a utility before it is created

should be able to create a domain from a long document

should be able to create a domain from multiple documents

should be able to see all schemas in the domain appearing in the inventory

should be able to update the schema

should be able to see updated changes of schema in the inventory

should be able to see changed domain schemas when selecting the domain during asset creation

should not be able to update an utility asset in the inventory that current user didn't create

should not be able to update an curated data asset in inventory that current user didn't create

should be able to update all curated data asset fields when it is in draft

should be able to update all curated data asset fields before it is sold at least once

should not be able to update any field after curated data asset sold at least once

different onboarded user should be able to find the asset in marketplace where searching using text similar (not identical) to the description of the published asset

should user be able to purchase the asset using metered method

should user be able to consume the curated data asset and metered unit should be deducted

should user be able to consume the curated data asset with no KF or MKF using relevant agent/widget

should user be able to consume the curated data asset using a relevant agent/widget with KF

should user be able to consume the curated data asset using a relevant agent/widget with MKF

should user be able to deactivate the asset

should not be able to consume an inactive curated data asset

should user be able to activate the inactive asset

should not be able to update any field after curated data asset sold at least two or more

should not be able to create more than 10 assets in draft status

should be able to create an asset in draft status after deleting an existing asset

should be able to publish a widget from studio (no other published assets)

should be able to perform searches less than 10

should be able to publish agent

should be able to publish an agent (second asset)

should be able to publish dataset

should be able to publish media

should be able to publish model

should be able to manually increase wallet balance to 20 DAAC

should be able to update all asset fields before clicking create

should not be able to update domain, instruction, sources or pricing after it is created

should not be able to update domain, instructions, sources or pricing after it is published

should be able to update dda name, description, thumbnail, tags and prerequisites before it is published

should be able to publish a widget (second asset)

should be able to publish a dataset (second asset)

should be able to publish a media (second asset)

should be able to publish a model (second asset)

should be able to manually increase wallet balance to 100 DAAC

can create agent with instructions and sources referring to specific source types, and placeholders are created for all of them in the extended flow

cannot test created agent without uploading files to replace placeholders in the extended flow

cannot publish without successfully testing the agent in the extended flow

different onboarded user can find the published asset in marketplace using similar description text in the extended flow

different onboarded user can purchase the asset and see inventory, balance and transaction details in the extended flow

user with KF but no sources cannot activate the asset without uploading files to replace placeholders in the extended flow

user with MKF but no sources cannot activate the asset without uploading files to replace placeholders in the extended flow

user with KF and relevant sources can activate the asset with no need for manual action in the extended flow