๐Ÿงช Trello Testing Project

Comprehensive QA Testing Suite for Trello Web Application - Professional Portfolio Showcase

5 Test Cases
80% Pass Rate
1 Bug Found
100% Coverage
๐Ÿ› Quality Status

1 bug identified and documented

MEDIUM BUG_001

White Background Selection Creates Blue Gradient

๐Ÿ‘ฉโ€๐Ÿ’ป Professional Details

Created by: Patrycja Gontarek
Environment: Chrome 137.x, macOS Sequoia
Duration: 7 days (27/05 - 03/06/2025)
Version: 1.2

TC001

Verify successful login with valid credentials

Priority
High
Test Type
Positive Test
Feature
User Authentication
Status
Pass
Created By
Patrycja Gontarek
Executed Date
27/05/2025

๐ŸŽฏ Test Objective

To verify that registered users can successfully log into Trello using valid email and password combinations, and are redirected to their dashboard upon successful authentication.

๐Ÿ“‹ Preconditions

  • User has a valid registered Trello account
  • User is currently logged out
  • User has stable internet connection
  • Testing on supported browser (Chrome)

๐Ÿ“Š Test Data

Valid Email: testuser@example.com
Valid Password: ValidPassword123*
Browser: Chrome (Version 137.0.7151.56)
Test Environment: Production (trello.com)

Note: These are example formats. Create your own test account for actual execution.

๐Ÿ”ฌ Test Steps

Step No. Test Steps Expected Result Actual Result Status
1 Navigate to https://trello.com Trello homepage loads successfully with "Log in" button visible in top right corner Trello homepage loaded successfully with visible "Log in" button Pass
2 Click on "Log in" button User is redirected to login page with email and password fields displayed The login page showed successfully Pass
3 Enter valid email address in the email field Email is accepted, field shows no error validation Email is visible in the field Pass
4 Enter valid password in the password field Password is masked with dots/asterisks, "Show" icon is visible All elements displayed as expected Pass
5 Click on "Log in" button Loading indicator appears. User is authenticated. Redirected to dashboard The board with the logged-in user is visible Pass
6 Verify dashboard elements User's boards are displayed. Profile icon shows in top right, "Create" option is available Dashboard loaded successfully displaying 4 user boards in grid layout. Profile icon with user avatar visible. Blue 'Create' button prominently displayed. No console errors detected Pass

โœ… Post-conditions

  • User is successfully logged into Trello
  • User session is active
  • User can access all features available to their account type

๐Ÿ“ˆ Test Results

Executed Date: 28/05/2025
Executed By: Patrycja Gontarek
Overall Status: Pass
Defects Found: None

TC002

Verify registration with already registered email

Priority
High
Test Type
Negative Test
Feature
User Registration
Status
Pass
Created By
Patrycja Gontarek
Executed Date
27/05/2025

๐ŸŽฏ Test Objective

To verify that the system prevents users from creating duplicate accounts with an email address that is already registered in Trello, and displays appropriate error messaging.

๐Ÿ“‹ Preconditions

  • Tester has access to an email that is already registered in Trello
  • User is on a cleared browser (no cached data)
  • User is not logged into any Trello account
  • Stable internet connection

๐Ÿ”ฌ Test Steps

Step No. Test Steps Expected Result Actual Result Status
1 Navigate to https://trello.com Trello homepage loads with "Create an account" button visible Trello homepage loaded with blue link "Create an account" Pass
2 Click on "Create an account" button Registration page loads with email field and "Sign up" button Registration page loaded with email field and blue "Sign up" button Pass
3 Enter an already registered email address Email is accepted in the field, no immediate validation Email address appeared in the field Pass
4 Click "Sign up" button System checks email availability. Error message appears. User remains on registration page System checked email availability and immediately redirected to "Log in to continue" page Pass
5 Verify error message content on login page Error shows "An account with this email already exists" or similar user-friendly message Error showed: "It looks like you've already got an account associated with this email. Log in instead or reset your password if you've forgotten it" Pass
6 Verify page behaviour after error Email field retains the entered value. User can proceed to login Email address pre-filled in the form field. Blue "Log in" button is provided. User can modify email and try to log in to existing account Pass

๐Ÿ” Findings & Observations

UX Enhancement/Positive Observation
During test execution, I discovered that Trello implements an intelligent redirect flow instead of traditional inline error messaging:

Expected: Error message on registration page
Actual: Automatic redirect to login page with pre-filled email
Impact: Saves users 5-10 seconds and reduces friction

This demonstrates superior UX design thinking by assuming user intent (existing user forgot they have account) rather than treating as error.

TC003

Verify logout functionality

Priority
High
Test Type
Positive Test
Feature
User Logout
Status
Pass
Created By
Patrycja Gontarek
Executed Date
29/05/2025

๐ŸŽฏ Test Objective

To verify that users can successfully logout from Trello, ensuring proper session termination, security handling, and consistent behavior across multiple tabs.

๐Ÿ“‹ Preconditions

  • User is successfully logged into Trello
  • User has at least one board open
  • Two browser tabs are open with Trello
  • Browser DevTools is open to monitor cookies/network

๐Ÿ”ฌ Test Steps

Step No. Test Steps Expected Result Actual Result Status
1 Open Trello in 2 tabs, ensure both show logged-in state Both tabs display user profile, boards, and authenticated content Found user profile avatar in top-right corner, boards displayed in the middle, authenticated content visible Pass
2 In DevTools > Application > Cookies, note auth cookies Should see authentication cookies including 'cloud.session.token' Found multiple auth cookies: cloud.session.token (991 bytes), atlassian.account.xsrf.token, atlUserHash, and 15+ other cookies Pass
3 Copy board URL and click profile avatar (top-right corner) Dropdown menu appears with account options including "Log out" Various options were found in the dropdown, including "Log out" Pass
4 Click "Log out" option Logout process initiates (may show loading or confirmation) Redirected to "Log out of your Atlassian account" with visible blue "Log out" button Pass
5 Click blue "Log out" button Redirected to Trello homepage with "Log in" option visible Successfully redirected to homepage with "Log in" option in upper right corner Pass
6 Check second browser tab Tab should show logged-out state on refresh/action Tab displayed "Page not found. This page may be private. You must log in to view it." Pass
7 In first tab, click browser back button Should NOT return to authenticated pages Website loaded on "Log out of your Atlassian account", no access to previous authenticated content Pass
8 Try accessing copied board URL Should show login prompt or error, not show board content Displayed "Page not found" with message "This page may be private. You must log in to view it" Pass
9 Open DevTools > Application > Cookies Session cookies should be cleared/expired Main session token cleared. Some Atlassian ecosystem cookies persist (by design) Pass
10 Go to Network tab, refresh page and check API calls Should block access to user data GET request returns 200 OK but with error page content (no user data exposed). Page shows login prompt Pass

๐Ÿ” Findings & Observations

1. Persistent Atlassian Ecosystem Cookies (Expected Behavior)
Some cookies remain after logout: __aid_user_id, atlUserHash, hasAccount=atlassian
Assessment: This is by design for Atlassian's cross-product features
Security Impact: None - these cookies cannot grant access to Trello resources
2. API Endpoints Return 200 OK with Error Page (Expected Behavior)
Board endpoints return 200 OK but serve error pages
Assessment: Common practice - status code indicates page loaded successfully
Security Impact: None - actual content shows login prompt, no data exposed
3. Proper Session Termination Confirmed
Critical session token (cloud.session.token) is properly cleared
All attempts to access user resources result in login prompts
No user data accessible post-logout

TC004

Create and Configure a New Board

Priority
High
Test Type
Positive Test
Feature
Board Management
Status
Partial Pass
Created By
Patrycja Gontarek
Executed Date
30/05/2025

๐ŸŽฏ Test Objective

To verify that authenticated users can successfully create a new Trello board with custom configurations, including board name, visibility settings, and background selection, ensuring proper board initialization and access control.

๐Ÿ“‹ Preconditions

  • User is successfully logged into Trello
  • User has permissions to create boards (free tier allows up to 10 boards)
  • User is on the main dashboard
  • Browser DevTools is available for monitoring network requests

๐Ÿ”ฌ Test Steps (Key Steps Shown)

Step No. Test Steps Expected Result Actual Result Status
1 From dashboard, click blue "Create" button Dropdown menu appears with "Create board" option Dropdown displayed with "Create board" and "Start with a template" options Pass
4 Select white background (first option) White background should be selectable and highlighted White background was available and highlighted with black checkmark Pass
7 Click "Create" button Loading indicator appears, button shows disabled state Button showed brief loading state, then modal closed. Network showed POST request Pass
8 Verify board creation success Redirected to new board URL with white background and "Add another list" option Successfully redirected to new board but showing gradient-bubble blue background instead of selected white, with 3 default lists: "To Do", "Doing", "Done" Partial Pass - Bug Found
12 Check API response for background setting Response should include background: "white" API returned background: "gradient-bubble" instead of "white" Partial Pass

๐Ÿ” Findings & Observations

1. Default Board Configuration
Observation: Three default lists are created: "To Do", "Doing", "Done"
Assessment: Follows standard Kanban methodology
User Impact: Immediate usability without additional setup
2. Background Color Inconsistency (BUG_001)
Observation: Selected white background appears as gradient-bubble
Assessment: Potential UI/backend synchronization issue
Impact: Minor visual discrepancy, functionality not affected
3. Performance Metrics (Within Acceptable Range)
Board Creation: ~1.2 seconds from click to redirect
API Response: 847ms for POST /1/boards endpoint
Page Load: 2.1 seconds to fully interactive state

TC005

Card lifecycle management and data persistence

Priority
High
Test Type
Hybrid (Scripted + Exploratory)
Feature
Card Management
Status
Pass
Created By
Patrycja Gontarek
Executed Date
06/06/2025

๐ŸŽฏ Test Objective

To verify that users can successfully create, modify, and manage cards throughout their complete lifecycle, ensuring data integrity, proper state transitions, and business rule compliance across different user interactions and system conditions.

๐Ÿ”ฌ Test Steps - Part A: Core Functionality (Key Steps)

Step No. Test Steps Expected Result Actual Result Status
1 In "To Do" list, click "Add a card" button Card creation interface appears with text input field active Card creation interface appeared with "Enter a title or paste a link" input field Pass
2 Type "Review QA documentation" and click "Add a card" Card created instantly, appears in "To Do" list with entered title Card "Review QA documentation" created in "To Do" list with interactive elements on hover Pass
5 Add checklist "Documentation Tasks" with 3 items Checklist created with 3 unchecked items, progress shows 0/3 Checklist "Documentation Tasks" created with 3 items, showing 0% progress Pass
7 Drag card from "To Do" to "Doing" list Card moves smoothly with visual feedback Card successfully moved to "Doing" list. Network captured multiple requests Pass
9 Refresh entire page (F5). Verify all data persists After refresh: Card in "Doing" list, description saved, checklist shows 1/3 Card persists in "Doing" list with all data intact - title, description, checklist (1/3), due date Pass

๐Ÿ”ฌ Test Steps - Part B: Exploratory Testing (Key Steps)

Test Type Test Steps Expected Result Actual Result Status
Character Limit Create card with 500+ character Lorem ipsum text Either truncation warning or proper handling of long text Long text displays with scroll capability. Minor sticky header overlap in modal view but text remains readable Pass
XSS Test Create card with `<script>alert('XSS')</script>` Script tags escaped, no alert shown No alert displayed, script tags rendered as text. Properly escaped in network payload Pass
Unicode Test Create card with emojis and special characters All characters display correctly without encoding issues All emojis and special characters displayed correctly. No console errors Pass
Rapid Fire Create 5 cards as fast as possible All cards created or rate limiting kicks in All 5 cards created successfully in correct order. No rate limiting observed Pass

๐Ÿ” Findings & Observations

1. Robust Data Persistence Mechanism
Observation: All card data persisted correctly across page refresh and browser tabs
Assessment: Real-time synchronization working as expected with proper API calls
Impact: Ensures data integrity and consistent user experience across sessions
2. Strong Security Implementation
Observation: XSS attempt properly escaped and rendered as plain text
Assessment: Input sanitization working correctly, preventing script injection attacks
Security Impact: Protects users from malicious code execution
3. Comprehensive Unicode Support
Observation: Emojis, special characters, and multilingual text rendered correctly
Assessment: Proper UTF-8 encoding throughout the application
Impact: Supports global user base with diverse language requirements
4. Excellent Performance Under Load
Observation: Rapid creation of 5 cards completed successfully without failures
Assessment: Backend handles concurrent requests efficiently
Performance Impact: Supports power users and bulk operations

๐Ÿ› BUG_001

White Background Selection Creates Blue Gradient

MEDIUM SEVERITY HIGH PRIORITY
๐Ÿ“ Found In

TC004 - Create and Configure a New Board
During board creation background selection process

๐Ÿ“… Discovery Date

30/05/2025
During Step 8 of TC004 execution

๐Ÿ”ง Environment

Chrome 137.0.7151.56
macOS Sequoia 15.5
Production (trello.com)

๐Ÿ‘ฉโ€๐Ÿ’ป Reported By

Patrycja Gontarek
QA Tester

๐ŸŽฏ Bug Description

When a user selects the white background option during board creation, the system creates the board with a blue gradient background instead of the selected white background. This creates a discrepancy between user selection and the actual board appearance.

๐Ÿ”„ Steps to Reproduce

  1. Log into Trello and navigate to dashboard
  2. Click the blue "Create" button in top navigation
  3. Select "Create board" from dropdown
  4. Enter any board name
  5. Select the white background (first option in background selector)
  6. Confirm the white background is highlighted with checkmark
  7. Click "Create" button
  8. Observe the created board background

๐ŸŽฏ Expected Behavior

Expected: Board should be created with white/plain background as selected by user during board creation process.

โŒ Actual Behavior

Actual: Board is created with "gradient-bubble" blue background instead of the selected white background.

๐Ÿ” Technical Evidence

๐Ÿ–ฅ๏ธ UI Evidence

โ€ข White background option was successfully selected in UI
โ€ข Checkmark overlay confirmed selection
โ€ข No error messages during creation process

๐Ÿ”Œ API Evidence

โ€ข POST /1/boards request sent successfully
โ€ข API response shows: background: "gradient-bubble"
โ€ข Expected: background: "white" or similar

๐ŸŒ Browser Evidence

โ€ข DevTools Network tab captured API mismatch
โ€ข No JavaScript console errors
โ€ข Background preference not preserved in request

๐Ÿ“Š Impact Analysis

๐Ÿ‘ฅ User Impact

Scope: All users creating boards with white background
Frequency: Every time white background is selected
Severity: Minor visual discrepancy, functionality not affected

๐Ÿ’ผ Business Impact

Priority: High (user experience/trust issue)
Revenue Impact: Low
Brand Impact: Minor consistency issue

๐Ÿ”ง Root Cause Hypothesis

Likely Causes:

  • UI/Backend Sync Issue: Frontend selection not properly transmitted to backend
  • Default Override: Backend defaulting to gradient-bubble when white selection fails
  • Mapping Error: White background option mapped to wrong backend value
  • Validation Issue: White background not recognized as valid option by backend

๐Ÿ’ก Recommended Solution

Investigation Steps:

  1. Verify frontend background selection value transmission
  2. Check backend validation logic for background options
  3. Review mapping between UI selections and backend values
  4. Test other background options for similar issues
  5. Implement proper error handling for invalid background selections

๐ŸŽฏ Acceptance Criteria for Fix

  • โœ… User selects white background โ†’ Board created with white background
  • โœ… API response matches user selection
  • โœ… No regression in other background options
  • โœ… Proper error handling if selection fails
  • โœ… Consistent behavior across all browsers

๐Ÿ“‹ TEST PLAN

Trello Web Application

5
Test Cases
80%
Pass Rate
1
Bug Found
7
Days

๐ŸŽฏ 1. Introduction

Purpose: This test plan outlines the testing approach for Trello's web application core features
Scope: Free tier functionality of Trello web app (desktop browsers)
Objective: Identify bugs, verify functionality, and ensure quality user experience

๐Ÿงช 2. Test Items

  • User Authentication (Login/Logout)
  • User Registration (Duplicate email validation)
  • Board Management (Create and Configure)
  • Card Functionality (Lifecycle and data persistence)

๐Ÿ”ฌ 4. Testing Approach

Testing Type: Manual Functional Testing
Testing Levels: System Testing
Testing Methods:
  • Positive testing (valid inputs)
  • Negative testing (invalid inputs)
  • Boundary value testing
  • Exploratory testing
  • Security testing (XSS attempts)
  • Performance monitoring (DevTools)
  • Hybrid testing (Scripted + Exploratory)

๐Ÿ“ฆ 8. Test Deliverables

Test Cases (5):
Bug Reports:
๐Ÿ› BUG_001: White Background Selection Creates Blue Gradient

๐Ÿ“Š 11. Test Summary

Total Test Cases Planned: 5
Test Cases Executed: 5
Pass: 4
Partial Pass: 1
Fail: 0
Bugs Found: 1 (Medium severity, High priority)
Overall Pass Rate: 80%

โœ… 12. Approval

Created by: Patrycja Gontarek
Date: 26/05/2025
Last Updated: 03/06/2025
Version: 1.2
Duration: 7 days (27/05 - 03/06/2025)