Skip to main content
PolinaKr
Community Manager
February 12, 2026

AI vs Human Meetup [Group Activity]

  • February 12, 2026
  • 12 replies
  • 300 views

Group Activity (35 min)


This is a team-based activity where groups use AI + human insight to craft a test strategy for a real feature/scenario. You have to collaborate, critique AI output, and produce a stronger end result together.

Objective: Build a test strategy that combines AI speed with human critical insight.

Time: 35 minutes

Submission: One post per team in this thread
 

1️ Setup a Team

  • Assign a group leader.
  • Assign a group name.
  • Write down the names of all members in your group

 

2️ Understand Activity Mission

Produce a test strategy for ShiftSync that covers testing across the key platform features you explored earlier.

Core features to include as test strategy areas:

  • Search Feature
  • Create Topic Feature
  • Community Zone
  • My Profile
  • User Profile → Settings

 

Note: Treat these features as the core part of your test strategy.
 

3️ Use AI to Produce a Baseline Strategy

Collaboratively craft a prompt to ask your AI tool for a comprehensive test strategy covering all the core features above.

Example starter prompt (tailor as per your creativity):

Generate a test strategy for the ShiftSync platform that includes Search, Create Topic, Community Zone, My Profile, and User Profile → Settings. Include functional tests, edge cases, risks, security considerations, and performance areas.

Run the prompt and capture:

  • The original prompt
  • The AI output

4️ Analyse the AI output

As a team, analyze what the AI strategy did well and did poorly.

Document at least 4 specific weaknesses or gaps, such as:

  • Things the AI missed entirely
  • Incorrect assumptions about how ShiftSync features work
  • Lack of testing for platform-specific risks
  • Missing non-functional concerns (performance, security, usability)
  • No prioritization of risks or test areas

 

Note: Be Specific - Name the missing test areas and why they matter to ShiftSync quality.

5️⃣ Draft a Human-Improved Test Strategy

Now build your final test strategy by combining:

  • AI’s original content where it’s useful
  • Human judgment to fix gaps
  • Expanded risk areas that are platform specific
  • Clear prioritization and actionable test directions

 

Note: Your strategy should be organized, concise, and practical.

📤 Submission:

Post your submission in this thread with the following detail:

🔹Submission Title: AI + Human Test Strategy | Team [Team Name] | ShiftSync Platform
🔹Team Member Names / ShiftSync IDs
🔹Attachments: Attach a document with all the below detail or copy paste text.

Your submission must include:

  1. Original Prompt
  2. AI Output (Original)
  3. List of AI Mistakes/Gaps (with reasoning)
  4. Final Human-Improved Test Strategy
  5. Optional Notes: Short reflection on what your team learned

 

Feel free to add your creative side or anything that helps us analyse your submission better.

    12 replies

    dharmendratak
    Ensign
    February 13, 2026

    Team Name: Team Of Leaders

    Team Members and Roles:

    Dharmendra Kumar (dharmendratak-3928) - Facilitated the Discussions and Documentation. Helped team to take some decisions.

    Ujjwal Kumar Singh (ujjwal-kumar-singh-5803) - Added his valuable feedback and worked on making document structure better.

    Petr Běloušek - Added his valuable feedback and provided some valueable key points during the discussion.

     

    Our team operated on a flat leadership structure where every member took full ownership of their specific module. While I facilitated the discussions and documentation, the strategic decisions and final outputs were the result of a collaborative feedback loop where all three members contributed equally. We have designated all members as 'Team Leads' to reflect this shared accountability and the high level of individual initiative shown by everyone. So we called it ‘Team of Leaders’.

     

    Deliverables:

    1. Original Prompt and AI Output : https://chatgpt.com/share/698df251-c154-800f-903f-3b7240b770d8
    2. List of AI Mistakes/Gaps : File attached - List of AI Mistakes Gaps.docx
    3. Final Human-Improved Test Strategy : File attached - Final Test Strategy.docx
    Dharmendra Kumar
    parwalrahul
    Navigator
    February 20, 2026

     

    Group Name: Strategical Thinkers

    Group Leader: Dinesh Gajarathi

    Members - Avni Aggarwa, Dinesh Gajarathi, Russell

     

    Original Prompts:

    --- I want to create a test strategy for my application with below key features: Search Feature Create Topic Feature Community Zone My Profile User Profile → Settings

    --- It is for shiftsync website. Please use details of "My Profile" feature that had article crerated

    --- Search feature includes- course/article/conversation Create topic feature- can start a conversation within community or we can create a question with details like category/title/description/tags Community Zone- where members can participate in discussion, ask question, start conversation, learn-can read blog/articles/videos/events

     

    AI Output (Original):

    # Test Strategy Document – ShiftSync Website

    ## 1. Introduction

    This document defines the test strategy for the **ShiftSync website**, outlining the approach, scope, and methods used to validate system quality and reliability.

    The strategy focuses on the following core features:

    * Search Feature
    * Create Topic Feature
    * Community Zone
    * My Profile (Layout)
    * User Profile → Settings

    ---

    ## 2. Objectives

    The objectives of testing are to:

    * Ensure all core features function correctly
    * Validate a smooth and intuitive user experience
    * Detect and prevent functional and security defects
    * Ensure proper data handling and persistence
    * Maintain system performance and stability

    ---

    ## 3. Scope of Testing

    ### In Scope

    * Functional validation of all listed features
    * UI/UX verification
    * Integration testing
    * Security and access control testing
    * Cross-browser compatibility testing
    * Basic performance checks

    ### Out of Scope

    * Internal testing of third-party systems
    * Infrastructure and hardware testing

    ---

    ## 4. Test Approach

    ### 4.1 Search Feature

    The Search feature enables users to search across **courses, articles, and conversations**.

    Testing will verify:

    * Accurate search results across courses, articles, and conversations
    * Keyword and partial keyword matching
    * Search result categorization and filtering
    * Handling of empty, invalid, or special character inputs
    * Relevance and ranking of search results
    * Performance and response time
    * UI display of search results

    ---

    ### 4.2 Create Topic Feature

    The Create Topic feature allows users to:

    * Start a conversation within the community
    * Create a question with structured details

    Testing will include:

    * Creation of conversations and questions
    * Field validations for:

    * Category
    * Title
    * Description
    * Tags
    * Mandatory field enforcement
    * Error messages and validation feedback
    * Successful submission and data persistence
    * Duplicate or invalid content handling
    * Permission and access control checks

    ---

    ### 4.3 Community Zone

    The Community Zone enables members to engage in learning and discussions.

    Users can:

    * Participate in discussions
    * Ask questions
    * Start conversations
    * Access learning content (blogs, articles, videos, events)

    Testing will focus on:

    * Navigation and accessibility of community sections
    * Posting and participation workflows
    * Viewing and interacting with discussions
    * Content display for blogs, articles, videos, and events
    * User engagement features
    * Access permissions and moderation behavior
    * Data consistency and session handling

    ---

    ### 4.4 My Profile (Layout Verification)

    The **My Profile** feature focuses on validating the layout and navigation of the profile landing page.

    Testing will cover:

    * Correct display of profile sections:

    * **Badges**
    * **About**
    * **User Activity** (Activity / Followers / Following)
    * UI layout consistency and responsiveness
    * Proper loading of user data
    * Visibility and functionality of the **Edit Profile** button
    * Navigation from **Edit Profile** to **User Profile → Settings**

    This section serves as a profile overview and navigation interface.

    ---

    ### 4.5 User Profile → Settings

    This feature manages profile editing and configuration.

    Testing will validate:

    **General**

    * Yes/No radio button behavior
    * Required field validation
    * Save Changes functionality
    * Data persistence after refresh or re-login

    **Notification**

    * Selection and saving of notification preferences
    * Correct application of notification settings

    **Password**

    * Password change workflow
    * Validation of current and new passwords
    * Error handling for invalid inputs
    * Security and encryption checks

    ---

    ## 5. Types of Testing

    The following testing types will be performed:

    * Functional Testing
    * Integration Testing
    * Usability Testing
    * Security Testing
    * Regression Testing
    * Performance Testing
    * Compatibility Testing

    ---

    ## 6. Test Environment

    Testing will be conducted in:

    * Staging/test environment
    * Supported browsers (Chrome, Firefox, Edge, Safari)
    * Desktop and mobile platforms

    ---

    ## 7. Test Data Management

    * Valid and invalid test inputs
    * Boundary and edge case scenarios
    * Role-based user accounts
    * Secure handling of sensitive test data

    ---

    ## 8. Defect Management

    * All defects will be logged in the tracking system
    * Each defect will include severity and priority levels
    * Retesting and regression testing will follow fixes

    ---

    ## 9. Risks and Mitigation

    ### Potential Risks

    * Incomplete requirements
    * Environment instability
    * Data inconsistencies
    * Security vulnerabilities

    ### Mitigation

    * Regular requirement reviews
    * Stable test environment maintenance
    * Controlled test datasets
    * Security validation practices

    ---

    ## 10. Tools

    * Test management tool (e.g., Jira/TestRail)
    * Bug tracking system
    * Browser developer tools
    * Optional automation tools

    ---

    ## 11. Deliverables

    * Test strategy document
    * Feature-based test cases
    * Test execution reports
    * Defect logs
    * Final test summary report

    ---

    ## 12. Exit Criteria

    Testing will be considered complete when:

    * All critical test cases pass
    * No high-severity defects remain open
    * Stakeholder approval is obtained

    ---

    Improved Prompts:

    Update tetsing types to: Functional Testing Integration Testing Usability Testing Regression Testing Performance Testing

     

     

    What was good in AI response:

    1. Nice template
    2. Added all teh information shared with GPT in the Test stragegy

     

    List of AI Mistakes/Gaps (with reasoning)

    1. Types of testing - assumed by GPT
    2. Defect management- Tools are missing, simply quoted about tracking system
    3. tools- no tools mentioned

     

    Final Human-Improved Test Strategy

    Test Strategy Document – ShiftSync Website

    1. Introduction

    This document defines the test strategy for the ShiftSync website, outlining the approach, scope, and methods used to validate system quality and reliability.

    The strategy focuses on the following core features:

    • Search Feature

    • Create Topic Feature

    • Community Zone

    • My Profile (Layout)

    • User Profile → Settings

    2. Objectives

    The objectives of testing are to:

    • Ensure all core features function correctly

    • Validate a smooth and intuitive user experience

    • Detect and prevent functional defects

    • Ensure proper data handling and persistence

    • Maintain system performance and stability

    3. Scope of Testing

    In Scope

    • Functional validation of all listed features

    • UI/UX verification

    • Integration testing

    • Cross-browser compatibility testing

    • Basic performance checks

    Out of Scope

    • Internal testing of third-party systems

    • Infrastructure and hardware testing

    4. Test Approach

    4.1 Search Feature

    The Search feature enables users to search across courses, articles, and conversations.

    Testing will verify:

    • Accurate search results across courses, articles, and conversations

    • Keyword and partial keyword matching

    • Search result categorization and filtering

    • Handling of empty, invalid, or special character inputs

    • Relevance and ranking of search results

    • Performance and response time

    • UI display of search results

    4.2 Create Topic Feature

    The Create Topic feature allows users to:

    • Start a conversation within the community

    • Create a question with structured details

    Testing will include:

    • Creation of conversations and questions

    • Field validations for:

      • Category

      • Title

      • Description

      • Tags

    • Mandatory field enforcement

    • Error messages and validation feedback

    • Successful submission and data persistence

    • Duplicate or invalid content handling

    • Permission and access control checks

    4.3 Community Zone

    The Community Zone enables members to engage in learning and discussions.

    Users can:

    • Participate in discussions

    • Ask questions

    • Start conversations

    • Access learning content (blogs, articles, videos, events)

    Testing will focus on:

    • Navigation and accessibility of community sections

    • Posting and participation workflows

    • Viewing and interacting with discussions

    • Content display for blogs, articles, videos, and events

    • User engagement features

    • Access permissions and moderation behavior

    • Data consistency and session handling

    4.4 My Profile (Layout Verification)

    The My Profile feature focuses on validating the layout and navigation of the profile landing page.

    Testing will cover:

    • Correct display of profile sections:

      • Badges

      • About

      • User Activity (Activity / Followers / Following)

    • UI layout consistency and responsiveness

    • Proper loading of user data

    • Visibility and functionality of the Edit Profile button

    • Navigation from Edit Profile to User Profile → Settings

    This section serves as a profile overview and navigation interface.

    4.5 User Profile → Settings

    This feature manages profile editing and configuration.

    Testing will validate:

    General

    • Yes/No radio button behavior

    • Required field validation

    • Save Changes functionality

    • Data persistence after refresh or re-login

    Notification

    • Selection and saving of notification preferences

    • Correct application of notification settings

    Password

    • Password change workflow

    • Validation of current and new passwords

    • Error handling for invalid inputs

    5. Types of Testing

    The following testing types will be performed:

    • Functional Testing

    • Integration Testing

    • Usability Testing

    • Regression Testing

    • Performance Testing

    6. Test Environment

    Testing will be conducted in:

    • Staging/test environment

    • Supported browsers (Chrome, Firefox, Edge, Safari)

    • Desktop and mobile platforms

    7. Test Data Management

    • Valid and invalid test inputs

    • Boundary and edge case scenarios

    • Role-based user accounts

    • Secure handling of sensitive test data

    8. Defect Management

    All identified defects will be tracked and managed using JIRA.

    • Defects will be logged with clear reproduction steps

    • Each defect will include severity and priority levels

    • Screenshots and logs will be attached when applicable

    • Defects will follow a defined lifecycle (Open → In Progress → Fixed → Retested → Closed)

    • Retesting and regression testing will be performed after fixes

    9. Risks and Mitigation

    Potential Risks

    • Incomplete requirements

    • Environment instability

    • Data inconsistencies

    Mitigation

    • Regular requirement reviews

    • Stable test environment maintenance

    • Controlled test datasets

    10. Tools

    • JIRA – Test and defect management

    • Browser developer tools

    • Optional automation tools

    11. Deliverables

    • Test strategy document

    • Feature-based test cases

    • Test execution reports

    • Defect logs

    • Final test summary report

    12. Exit Criteria

    Testing will be considered complete when:

    • All critical test cases pass

    • No high-severity defects remain open

    • Stakeholder approval is obtained

    Optional Notes: Short reflection on what your team learned

    It is a good community platform that enables to connect with brilliant minds focussing on same learning area. Activities helped to explore and learn AI.

     

    Congratulations to the Strategical Thinkers team for the win! 🎉

    @Avni, ​@Dinesh_Gujarathi, and ​@Russell — you are the winners of the group activity.

    The announcement was made yesterday during the AI Agents MasterClass, and it was a moment worth celebrating.

    Strong thinking. Clear execution. Deserved victory.

    Well done. Keep shining and keep raising the bar.

    Please reach out to ​@Mustafa and ​@PolinaKr for the next steps regarding your awards.

    https://testingtitbits.com/