11 Testing Scenarios For You to Try -DDRS Beta Test

Your Opportunity to Explore Decentralized Dispute Resolution System (DDRS)

Key Takeaways

• Campaign Duration: 19.12.2024–16.01.2025
• DDRS Beta Test Guide: DDRS Guide
• Rewards: $4.000
• DDRS Platform: DDRS
• Report Bug or Suggestion: Jira Portal
• Leaderboard: DDRS Leaderboard

Are you ready to take a deeper dive into the functionality of the Decentralized Dispute Resolution System (DDRS)?

The Beta Test for Module 1 is now live, giving participants the chance to explore DDRS’s core features, test real-world scenarios, provide valuable feedback to shape the platform’s future and win rewards of $4,000 in VAI token utility.

Start Testing Now! → https://ddrs.vaiot.ai/

Testing Scenarios to Guide Your Testing

We’ve prepared a series of real-world scenarios to help you explore the platform’s features. They are designed to test the system’s functionality, highlight potential areas for improvement, and ensure a seamless user experience.

Testing Scenarios — Decentralized Dispute Resolution System (DDRS)

Service Provider’s User Stories

User Story 1 — Smooth Path

• Scenario: You are a Service Provider tasked with designing a website for a Client (Ordering Party). You propose using DDRS for transparency and security.

Steps:

1. As the Service Provider, create the initial transaction terms, including the service description, acceptance criteria, deadline, and price.
2. Share the transaction with the Ordering Party. Use DDRS’s AI Assistant to structure the terms and acceptance criteria.
3. Accept all terms without negotiation on both sides.
4. Finalize the transaction, mark the service as “Delivered,” and complete the process by having the Ordering Party accept the service.

• Expected Outcome: The transaction should smoothly progress to the “Completed” state. Both parties should see the transaction in their respective dashboards.
• Feedback Request: Report any usability issues, unclear instructions, or areas for improvement through the JIRA portal.

User Story 2 — A “Difficult” Client

• Scenario: You are a Service Provider negotiating terms with a challenging Client.

Steps:

1. Create an initial transaction and share it with the Client.
2. As the Client, negotiate multiple terms (e.g., price, deadline, and acceptance criteria). Use the comments/chat feature to discuss changes.
3. Accept some proposals while renegotiating others. Continue until both parties agree on the final terms.

• Expected Outcome: The negotiation process should be smooth, with changes accurately reflected in the transaction details, chat history, and notifications.
• Feedback Request: Test the usability of the comments/chat, negotiation functions, and notifications. Report bugs or suggest improvements via JIRA.

User Story 3 — Service Not Delivered

• Scenario: The transaction is created and accepted, but the service is not delivered as expected.

Steps:
As the Service Provider, let the delivery deadline pass without marking the service as delivered. Observe the behavior of the platform.
Expected Outcome: The platform should handle overdue services showing updated statuses and notifying the Ordering Party.

• Feedback Request: Report any issues with status updates, notifications, or the handling of services not delivered on time.

Ordering Party’s User Stories

User Story 1 — Service Completion and Payment

• Scenario: You order a marketing strategy from a Service Provider and complete the transaction smoothly.

Steps:

1. Create a transaction with clear terms, including scope, acceptance criteria, deadline, and payment.
2. Share the transaction with the Service Provider, who accepts the terms without changes.
3. Approve the service completion after reviewing the delivered work.

• Expected Outcome: The transaction should conclude successfully, with both parties seeing the completed status and payment details in their transaction history.
• Feedback Request: Report any issues with the transaction status via JIRA.

User Story 2 — Renegotiating Terms Before Payment

• Scenario: You negotiate terms with a Service Provider for a graphic design project.

Steps:

1. Propose initial terms, including scope, deadline, and payment.
2. Review the Service Provider’s counterproposal and renegotiate terms (e.g., deadline).
3. Finalize the updated contract and complete the transaction.

• Expected Outcome: The renegotiation process should be smooth, with all updates accurately reflected.
• Feedback Request: Report any issues with negotiations or contract updates via JIRA.

User Story 3 — Managing Multiple Transactions

• Scenario: You manage three transactions simultaneously.

Steps:

1. Create three transactions for different services (e.g., logo design, blog writing, and document translation).
2. Monitor progress from the dashboard and test filtering options for transaction statuses.
3. Complete each transaction one by one and verify updates.

• Expected Outcome: The dashboard should handle multiple transactions seamlessly, with accurate progress updates and filtering options.
• Feedback Request: Report usability issues or suggestions for managing multiple transactions via JIRA.

General User Stories

User Story 1 — Platform Onboarding Experience

• Scenario: You are a first-time user exploring DDRS.

Steps:

1. Connect your wallet to the platform.
2. Use the AI Assistant to guide you through creating a new transaction.
3. Test the Assistant’s ability to provide clear, helpful instructions during onboarding.

• Expected Outcome: The onboarding process should be intuitive, with the AI Assistant providing relevant and actionable guidance.
• Feedback Request: Report any confusion, unclear instructions, or suggestions for improvement via JIRA.

User Story 2 — Leveraging the AI Assistant

• Scenario: You use the AI Assistant to enhance a transaction agreement.

Steps:

1. Ask the Assistant for help with structuring acceptance criteria, defining milestones, or clarifying deliverables.
2. Incorporate the Assistant’s suggestions into the terms and finalize the contract.

• Expected Outcome: The AI Assistant should provide practical and relevant suggestions that improve the quality of the transaction terms.
• Feedback Request: Test the Assistant’s capabilities and report any irrelevant or unhelpful recommendations through JIRA.

User Story 3 — Cross-Device (Cross-Platform) User

• Scenario: You want to test DDRS functionality across multiple devices.

Steps:

1. Start creating a transaction on a desktop device and define agreement terms.
2. Switch to a mobile device and continue editing or finalizing the transaction.
3. Complete the transaction and verify the process on both devices.

• Expected Outcome: The platform should function seamlessly across devices, maintaining responsiveness and usability.
• Feedback Request: Report any inconsistencies or usability challenges while switching devices via JIRA.

User Story 4 — Role-Switching Between Ordering Party and Service Provider

• Scenario: You act as both an Ordering Party and a Service Provider to test role-specific functionalities.

Steps:

1. Register with separate wallets for each role.
2. Switch between roles and test creating contracts, reviewing terms, and delivering services.

• Expected Outcome: The platform should handle role-specific actions without errors or confusion.
• Feedback Request: Test for role-based functionality issues and report via JIRA.

User Story 5 — Exploring Offline Work

• Scenario: You simulate being offline during a transaction and then reconnect to review updates.

Steps:

1. Create a transaction and go offline for a period.
2. Log back in and review updates, such as new messages, contract changes, or service completions.

• Expected Outcome: Notifications should be clear and comprehensive, allowing you to catch up on missed updates.
• Feedback Request: Report any issues with offline notifications or updates via JIRA.

Let’s Build the Future Together

The DDRS Beta Test is your opportunity to help shape the future of decentralized transaction management and dispute resolution.

Dive into the platform, explore different roles and scenarios, and let us know how we can make DDRS even better.

Ready to get started?

Head over to DDRS, connect your wallet, and begin testing today!

About VAIOT

VAIOT offers LegalTech and DeLaw solutions to democratize access to legal services by leveraging AI and Blockchain. Proudly, we are the first VFAA-regulated digital asset issuer.

VAIOT- AI and Blockchain for Legal Innovation.

Read our AI Legal Assistant Lightpaper here.

For more information about VAIOT, visit our website www.vaiot.ai, or join our Twitter , Telegram Community, Discord Server or Youtube Channel for continuous updates.

By participating in VAIOT’s DDRS Beta Testing Campaign and related Gleam campaign you hereby acknowledge that you have read, understood, and accepted the DDRS Privacy Policy, which describes how your personal data will be processed, and Gleam campaign’s Terms and Conditions. You consent to the use of cookies and tracking technologies in accordance with the DDRS Privacy Policy and confirm that you are at least 16 years of age (or have parental/guardian consent if younger).

The VAIOT Website, Platforms, Solutions, and Services, and in particular VAI Tokens, are not offered for use and purchase to natural and legal persons having their permanent residence or their seat of incorporation in any of the restricted areas as listed in VAIOT’s Whitepaper, in particular: USA, Germany, Puerto Rico, US Virgin Islands, Canada, China, Singapore, Afghanistan, Central African Republic, Cuba, Democratic Republic of the Congo, Eritrea, Iran, Iraq, Libya, North and South Korea, Somalia, South Sudan, Sudan, Yemen, Zambia (Restricted Areas).