FutureOS AI Platform QA Testing

$30-250 CAD

Posted 1 minute ago

•

Ends in 6 days

$30-250 CAD

Paid on delivery

Freelance QA Tester for FutureOS AI Agents — Full Website and Platform Testing We’re looking for an experienced QA tester to test FutureOS AI Agents, a platform where businesses manage AI agents, content, marketing campaigns, and third-party integrations. Each client has its own workspace, users, settings, and budget. Your assignment is to test the entire website from the perspective of a visitor, a customer, and an administrator. We want to know whether a new customer can sign up, set up their business, run a workflow, find the result, and understand what to do if something goes wrong. Scope of work - Public website and accounts — Test landing pages, pricing, navigation, links, forms, registration, email verification, login, password reset, and logout. - Dashboards and workspaces — Test onboarding, menus, account settings, roles, and switching between businesses. Using two test workspaces, verify that each displays its own content, contacts, integrations, and budget. - AI agents and automations — Test each available agent and its chat assistant. Run manual and scheduled workflows, follow tasks through the queue, and compare the reported status with the actual result. Check what happens when a task fails or is retried. - Blogs and video creation — Create, edit, review, translate, and publish a test article to an approved destination. Check its formatting and images. Then turn the article into a video and verify that the exported file opens and plays with the expected visuals and narration. - Influencer and social media tools — Search by niche and minimum follower count. Open the profiles, verify the displayed audience information, save selected creators, and test the invitation process using a designated test recipient. - Integrations, billing, and administration — Test the available social, email, and e-commerce connections, including expired or disconnected accounts. Check plans, subscriptions, usage limits, notifications, and admin controls. Use test mode for payments. - Desktop and mobile usability — Check the main customer journeys in Chrome and Safari on desktop and mobile. Flag broken layouts, unreadable text, confusing navigation, and buttons that give no feedback. What we expect you to deliver 1. A coverage checklist showing every page and workflow tested, the role and browser used, and the outcome: passed, failed, or blocked. For blocked tests, identify what you need to complete them. 2. A prioritized bug report with one issue per entry. Include severity, the affected page, steps to reproduce, expected and actual results, and a screenshot or short recording when helpful. 3. A launch-readiness summary identifying which issues prevent customers from completing essential tasks and which can be addressed after launch. 4. One retest round after our developer delivers fixes, with an updated status for each reported issue. We’ll coordinate test accounts and approved test destinations before testing begins. Use test data for invitations, publishing, payments, and AI workflows that consume credits. How to apply Please include your experience testing SaaS platforms, a sample bug report with confidential details removed, the browsers and devices you can cover, your earliest start date, your estimated turnaround, and your fixed-price quote for the full audit and one retest round. Please also answer this short question: If an AI workflow shows “Completed” but the customer cannot find the generated article, how would you test and document the issue?

Project ID: 40830675

About the project

17 proposals

Open for bidding

Remote project

Active 6 secs ago

Place your bid

Bid amount Email address

Benefits of bidding on Freelancer

Set your budget and timeframe

It's free to sign up and bid on jobs

17 freelancers are bidding on average $114 CAD for this job

User Avatar
Flag of PAKISTAN

Greetings, I’m excited about the opportunity to work on the QA testing for the FutureOS AI Platform. It sounds like you need thorough testing from various perspectives—visitor, customer, and admin—to ensure everything runs smoothly. My approach would involve testing each aspect of the platform, from the public website to the AI agents and integration tools, ensuring that every user journey is seamless and intuitive. With my experience in testing SaaS platforms, I’m skilled at creating detailed coverage checklists and bug reports that clearly document each issue and its impact on user experience. I understand the importance of identifying critical issues before launch, and I’m committed to delivering a comprehensive summary that highlights any blockers. I look forward to contributing to the success of FutureOS! Best regards, Saba Ehsan

User Avatar
Flag of UNITED STATES

Hi - Adelman here from Texas SAAS PLATFORM QA TESTING - you need to know whether customers can complete real workflows without hidden failures. I'd test FutureOS from visitor, customer, and admin roles, using two separate workspaces to catch data leaks and permission issues. I'd also trace AI jobs from submission to queue, completion, and the actual saved output, then document reproducible bugs with severity, screenshots, and clear steps. I can cover Chrome and Safari on desktop and mobile, including one retest round. If an AI workflow says "Completed" but the article is missing, I'd check the job ID, queue status, API response, database record, and destination. I'd document where the process breaks, what the customer sees, and the steps to reproduce it. Can you provide two test workspaces and the approved destinations before testing begins? Looking forward to work with you.

User Avatar
Flag of PAKISTAN

I'll run a full QA audit of FutureOS AI Agents so a new customer can sign up, set up a business, run an AI workflow, find results, and know what to do if something goes wrong. I'll test the public site, registration and email flows, dashboards and workspace isolation, onboarding and roles, AI agents and scheduled workflows, blog to video publishing, influencer tools, integrations, billing in test mode, and desktop and mobile usability in Chrome and Safari. You will receive: - a coverage checklist by page, role and browser with pass fail or blocked status - a prioritized bug list with severity, steps to reproduce, expected and actual result, and screenshots or short recordings - a launch readiness summary calling out blockers - one retest round with updated statuses My experience includes testing multi workspace SaaS, billing and third party integrations for platforms that manage content and automations. Browsers and devices I cover: Chrome desktop and mobile, Safari desktop and mobile, Firefox desktop, Edge desktop, iOS and Android phones. Sample bug report Title: Generated article missing after workflow shows Completed Severity: High Page: Workspace > Content Library Steps: Run Agent X with template Y. Observe workflow status Completed. Open Content Library and search for title. Expected: article appears. Actual: not found. Evidence: workflow log screenshot, queue entry screenshot, empty search result recording. Notes: check storage path, indexing, permissions, and content attachments. If a workflow shows Completed but the article is missing I will check the agent logs, queue item details, storage location, content index, permissions, and attempt a rerun while capturing logs and artifacts so developers can reproduce and fix. I'm ready to start. When would you like to kick things off? Best, Chand

User Avatar
Flag of UNITED STATES

Hi, Multi-workspace AI platforms can look healthy while quietly losing the handoff between a completed job and the customer-facing result; that’s where launch confidence gets tested. I’d map the visitor, customer, and admin journeys, then run the agreed test data through each workflow and record role, browser, outcome, and reproducible evidence. A sample issue could read: “High , Article generation , completed status shown, no article in workspace; steps to reproduce, expected result, actual result, screenshot.” For a “Completed” article that’s missing, I’d capture the workspace, agent, run ID and time, then check queue history and destination before documenting whether output was never created, saved elsewhere, or hidden by permissions. The main risk is separating a generation failure from a visibility or workspace-isolation bug; same symptom, very different fix. Browser/device coverage, start date, turnaround, and fixed quote can be set once access and the test matrix are confirmed. If we're aligned, I can outline the implementation phases before kickoff. Best regards, Brandon

User Avatar
Flag of UNITED STATES

Hello [Client's Name], I am Dominique, an experienced QA tester with a strong background in SaaS platforms and automation testing, eager to assist with the comprehensive testing of FutureOS AI Agents. Your project requires a thorough evaluation from multiple perspectives, and I am well-equipped to deliver a meticulous and insightful analysis. Understanding the complexities of managing AI agents, content, and integrations, I will employ a methodical approach to cover every aspect of the platform. My experience in testing public websites, dashboards, AI-driven processes, and integration functionalities will ensure a comprehensive examination of the user experience from visitor to administrator. I have a proven track record in identifying critical issues, ensuring that workflows are seamless and user-friendly. For the outlined scope, I will conduct detailed tests across various browsers and devices, documenting every page and workflow with precision. My deliverables will include a detailed checklist, a prioritized bug report, and a launch-readiness summary, ensuring that FutureOS is robust and ready for the market. In response to your question, if a workflow shows “Completed” but the article is missing, I would verify the workflow logs, check the storage location, and examine any error messages or logs indicating a failure in the process. This would include screenshots and detailed steps to reproduce the issue for the development team. I look forward to the opportunity to contribute to the success of FutureOS with a thorough and insightful QA process. Best regards, Dominique

User Avatar
Flag of TURKEY

I can conduct a structured end-to-end QA audit of FutureOS, focusing on customer journeys, workspace isolation, AI workflow reliability, integrations, and launch readiness. I'll test the platform from visitor, customer, and administrator perspectives, covering registration, onboarding, dashboards, multi-workspace data separation, AI agents, automations, content generation, video exports, social tools, integrations, billing, and admin controls. For every issue, I'll document reproducible steps, expected versus actual results, severity, affected browser and role, and supporting screenshots where useful. I'll pay special attention to failed AI tasks, incorrect completion statuses, and cross-workspace data leakage. AI workflow question: If a workflow shows "Completed" but the article is missing, I'll trace the task through execution logs, API responses, and content storage. I'll verify whether it was generated, saved, assigned to the correct workspace, and displayed in the dashboard. I'll document reproduction steps, evidence, impact, and the likely failure point. You'll receive a coverage checklist, prioritized bug report, launch-readiness summary, and one retest round after fixes. I'll confirm the final timeline and fixed price based on the number of agents, integrations, and test environments.

内容来自 Freelancer News,版权归原作者所有。

阅读原文 ↗

用 HomepageTab 新标签页关注 RSS,打开浏览器就能看到更新。

安装 HomepageTab