e2e-output.txt


Running 220 tests using 8 workers

  ✓    3 [chromium] › e2e\admin-and-analytics.spec.ts:9:7 › Admin Access › should require authentication to access admin dashboard (6.8s)
  ✓    1 [chromium] › e2e\admin-and-analytics.spec.ts:37:7 › Admin Access › should display admin navigation menu (7.0s)
  ✓    4 [chromium] › e2e\admin-and-analytics.spec.ts:64:7 › Analytics Dashboard › should display analytics dashboard (7.0s)
  ✓    2 [chromium] › e2e\admin-and-analytics.spec.ts:23:7 › Admin Access › should display admin dashboard for authorized users (7.1s)
  ✓    6 [chromium] › e2e\admin-and-analytics.spec.ts:92:7 › Analytics Dashboard › should display session analytics (8.2s)
  ✓    5 [chromium] › e2e\admin-and-analytics.spec.ts:52:7 › Analytics Dashboard › should navigate to analytics page (8.1s)
  ✓    9 [chromium] › e2e\admin-and-analytics.spec.ts:116:7 › Analytics Dashboard › should display revenue/billing analytics (4.0s)
  ✓   10 [chromium] › e2e\admin-and-analytics.spec.ts:129:7 › User Management › should display user list in admin panel (3.9s)
  ✓   11 [chromium] › e2e\admin-and-analytics.spec.ts:141:7 › User Management › should allow searching for users (3.9s)
  ✓   12 [chromium] › e2e\admin-and-analytics.spec.ts:155:7 › User Management › should display user details (4.6s)
  ✓   14 [chromium] › e2e\admin-and-analytics.spec.ts:179:7 › User Management › should allow filtering users by role/status (4.1s)
  ✓   13 [chromium] › e2e\admin-and-analytics.spec.ts:166:7 › User Management › should allow viewing user profile from admin (4.1s)
  ✓    7 [chromium] › e2e\admin-and-analytics.spec.ts:103:7 › Analytics Dashboard › should allow filtering analytics by date range (12.5s)
  ✓    8 [chromium] › e2e\admin-and-analytics.spec.ts:78:7 › Analytics Dashboard › should display user statistics (12.6s)
  ✓   15 [chromium] › e2e\admin-and-analytics.spec.ts:194:7 › Mentor Management › should access mentor management API (3.3s)
  ✓   16 [chromium] › e2e\admin-and-analytics.spec.ts:205:7 › Mentor Management › should display mentor list in admin (3.3s)
  ✓   18 [chromium] › e2e\admin-and-analytics.spec.ts:229:7 › Mentor Management › should display pending mentor applications (3.3s)
  ✓   19 [chromium] › e2e\admin-and-analytics.spec.ts:244:7 › Content Management › should display diet plans management (3.3s)
  ✓   20 [chromium] › e2e\admin-and-analytics.spec.ts:255:7 › Content Management › should allow creating new diet plans (3.4s)
  ✓   21 [chromium] › e2e\admin-and-analytics.spec.ts:268:7 › Content Management › should display subscription plans management (3.7s)
  ✓   22 [chromium] › e2e\admin-and-analytics.spec.ts:282:7 › Content Management › should allow editing plan details (3.6s)
  ✓   23 [chromium] › e2e\admin-and-analytics.spec.ts:297:7 › Moderation › should access moderation API (3.1s)
  ✓   24 [chromium] › e2e\admin-and-analytics.spec.ts:308:7 › Moderation › should display moderation dashboard (3.2s)
5 payment requests completed in 53ms
  ✓   31 [chromium] › e2e\api-load-testing.spec.ts:40:7 › Performance Testing - API Load Testing › should handle payment processing load (384ms)
  ✓   25 [chromium] › e2e\admin-and-analytics.spec.ts:321:7 › Moderation › should display reported content/issues (3.1s)
  ✘   30 [chromium] › e2e\api-load-testing.spec.ts:6:7 › Performance Testing - API Load Testing › should handle concurrent checkout API requests (515ms)
8 concurrent booking requests completed in 26ms
  ✓   33 [chromium] › e2e\api-load-testing.spec.ts:106:7 › Performance Testing - API Load Testing › should handle session booking requests under load (312ms)
  ✘   32 [chromium] › e2e\api-load-testing.spec.ts:75:7 › Performance Testing - API Load Testing › should handle mentor search under load (373ms)
12 filtered mentor requests completed in 9ms
  ✓   34 [chromium] › e2e\api-load-testing.spec.ts:175:7 › Performance Testing - API Load Testing › should handle mentor listing with various filters (197ms)
10 diet plan requests completed in 10ms
  ✓   26 [chromium] › e2e\admin-and-analytics.spec.ts:336:7 › System Management › should access debug/test endpoints (3.1s)
  ✓   35 [chromium] › e2e\api-load-testing.spec.ts:239:7 › Performance Testing - API Load Testing › should handle diet plan API under load (165ms)
  ✓   27 [chromium] › e2e\admin-and-analytics.spec.ts:348:7 › System Management › should access test endpoints (3.2s)
8 billing history requests completed in 17ms
15 subscription status requests completed in 11ms
  ✓   36 [chromium] › e2e\api-load-testing.spec.ts:266:7 › Performance Testing - API Load Testing › should handle billing API requests efficiently (197ms)
  ✓   37 [chromium] › e2e\api-load-testing.spec.ts:293:7 › Performance Testing - API Load Testing › should handle subscription status checks concurrently (199ms)
6 timeslot creation requests completed in 14ms
5 profile update requests completed in 15ms
  ✓   38 [chromium] › e2e\api-load-testing.spec.ts:320:7 › Performance Testing - API Load Testing › should handle timeslot creation requests (198ms)
  ✓   39 [chromium] › e2e\api-load-testing.spec.ts:355:7 › Performance Testing - API Load Testing › should handle profile update requests (199ms)
  ✘   40 [chromium] › e2e\api-load-testing.spec.ts:389:7 › Performance Testing - API Load Testing › should measure API response time distribution (226ms)
  ✓   17 [chromium] › e2e\admin-and-analytics.spec.ts:218:7 › Mentor Management › should allow approving mentor applications (8.6s)
  ✓   28 [chromium] › e2e\admin-and-analytics.spec.ts:359:7 › System Management › should access cron/automated tasks (3.3s)
  ✓   29 [chromium] › e2e\admin-and-analytics.spec.ts:370:7 › System Management › should access tickets/support system (3.7s)
20 authentication requests completed in 22ms
  ✓   45 [chromium] › e2e\api-load-testing.spec.ts:141:7 › Performance Testing - API Load Testing › should handle user authentication burst (288ms)
5 analytics requests completed in 18ms
  ✓   47 [chromium] › e2e\api-load-testing.spec.ts:212:7 › Performance Testing - API Load Testing › should handle analytics data aggregation under load (300ms)
  ✓   42 [chromium] › e2e\api-security.spec.ts:6:7 › Security Audit - API & Data Access › should validate API authentication headers (2.5s)
  ✓   46 [chromium] › e2e\api-security.spec.ts:75:7 › Security Audit - API & Data Access › should implement proper pagination (1.8s)
  ✓   43 [chromium] › e2e\api-security.spec.ts:42:7 › Security Audit - API & Data Access › should validate input parameters in APIs (4.1s)
  ✓   44 [chromium] › e2e\api-security.spec.ts:57:7 › Security Audit - API & Data Access › should not expose database errors (4.4s)
  ✘   41 [chromium] › e2e\api-load-testing.spec.ts:420:7 › Performance Testing - API Load Testing › should handle sustained API load (5.2s)
  ✓   50 [chromium] › e2e\api-security.spec.ts:32:7 › Security Audit - API & Data Access › should prevent unauthorized data access (3.9s)
  ✓   48 [chromium] › e2e\api-security.spec.ts:84:7 › Security Audit - API & Data Access › should validate JSON schema in API responses (5.6s)
  ✓   51 [chromium] › e2e\api-security.spec.ts:119:7 › Security Audit - API & Data Access › should prevent privilege escalation (4.5s)
  ✓   53 [chromium] › e2e\api-security.spec.ts:150:7 › Security Audit - API & Data Access › should implement proper request validation (6.1s)
  ✓   57 [chromium] › e2e\api-security.spec.ts:234:7 › Security Audit - API & Data Access › should validate and limit file upload sizes (3.7s)
  ✓   55 [chromium] › e2e\api-security.spec.ts:190:7 › Security Audit - API & Data Access › should not expose internal IDs in responses (6.5s)
  ✓   54 [chromium] › e2e\api-security.spec.ts:164:7 › Security Audit - API & Data Access › should prevent race condition attacks (8.2s)
  ✓   56 [chromium] › e2e\api-security.spec.ts:209:7 › Security Audit - API & Data Access › should implement proper access control lists (6.4s)
  ✓   49 [chromium] › e2e\api-security.spec.ts:102:7 › Security Audit - API & Data Access › should not allow admin operations without authorization (13.7s)
  ✓   58 [chromium] › e2e\api-security.spec.ts:173:7 › Security Audit - API & Data Access › should validate timestamps and prevent replay attacks (7.5s)
  ✓   60 [chromium] › e2e\api-security.spec.ts:264:7 › Security Audit - API & Data Access › should validate cache control headers (4.7s)
  ✓   59 [chromium] › e2e\api-security.spec.ts:248:7 › Security Audit - API & Data Access › should prevent HTTP header injection (7.7s)
  ✓   52 [chromium] › e2e\api-security.spec.ts:138:7 › Security Audit - API & Data Access › should sanitize query parameters (15.7s)
  ✓   62 [chromium] › e2e\auth-and-signup.spec.ts:21:7 › User Signup Flow › should display signup form with email and password fields (6.9s)
  ✓   63 [chromium] › e2e\auth-and-signup.spec.ts:37:7 › User Signup Flow › should show validation error for empty email field (7.6s)
  ✓   66 [chromium] › e2e\auth-and-signup.spec.ts:93:7 › User Login Flow › should display signin form on signin page (6.4s)
  ✓   64 [chromium] › e2e\auth-and-signup.spec.ts:49:7 › User Signup Flow › should validate email format on signup (6.7s)
  ✓   68 [chromium] › e2e\auth-and-signup.spec.ts:133:7 › User Login Flow › should have signup link on signin page (5.1s)
  ✓   61 [chromium] › e2e\auth-and-signup.spec.ts:9:7 › User Signup Flow › should navigate to signup page from home (11.0s)
  ✓   69 [chromium] › e2e\auth-and-signup.spec.ts:143:7 › User Login Flow › should navigate to signup from signin page (4.2s)
  ✓   67 [chromium] › e2e\auth-and-signup.spec.ts:112:7 › User Login Flow › should show error on signin with invalid credentials (6.4s)
  ✓   70 [chromium] › e2e\auth-and-signup.spec.ts:156:7 › Password Reset Flow › should display forgot password page (4.8s)
  ✓   72 [chromium] › e2e\auth-and-signup.spec.ts:184:7 › Password Reset Flow › should display reset password form with token (4.7s)
  ✓   75 [chromium] › e2e\auth-security.spec.ts:27:7 › Security Audit - Authentication & Authorization › should prevent session fixation (3.0s)
  ✓   74 [chromium] › e2e\auth-security.spec.ts:6:7 › Security Audit - Authentication & Authorization › should enforce strong password validation (3.7s)
  ✓   71 [chromium] › e2e\auth-and-signup.spec.ts:173:7 › Password Reset Flow › should navigate to forgot password from signin (5.6s)
  ✓   80 [chromium] › e2e\auth-security.spec.ts:91:7 › Security Audit - Authentication & Authorization › should use secure flag for auth cookies in production (217ms)
  ✓   76 [chromium] › e2e\auth-security.spec.ts:35:7 › Security Audit - Authentication & Authorization › should invalidate session on logout (3.2s)
  ✓   73 [chromium] › e2e\auth-and-signup.spec.ts:203:7 › Password Reset Flow › should show error for missing/invalid reset token (4.6s)
  ✓   79 [chromium] › e2e\auth-security.spec.ts:77:7 › Security Audit - Authentication & Authorization › should use secure HTTP-only cookies (3.4s)
  ✓   77 [chromium] › e2e\auth-security.spec.ts:43:7 › Security Audit - Authentication & Authorization › should prevent token leakage in URLs (5.0s)
  ✓   81 [chromium] › e2e\auth-security.spec.ts:104:7 › Security Audit - Authentication & Authorization › should use SameSite attribute on cookies (3.4s)
  ✓   83 [chromium] › e2e\auth-security.spec.ts:138:7 › Security Audit - Authentication & Authorization › should prevent email enumeration (3.6s)
  ✓   65 [chromium] › e2e\auth-and-signup.spec.ts:67:7 › User Signup Flow › should successfully complete signup form (16.4s)
  ✓   78 [chromium] › e2e\auth-security.spec.ts:56:7 › Security Audit - Authentication & Authorization › should prevent brute force attacks (8.9s)
  ✓   82 [chromium] › e2e\auth-security.spec.ts:117:7 › Security Audit - Authentication & Authorization › should protect password reset tokens (9.4s)
  ✓   84 [chromium] › e2e\auth-security.spec.ts:152:7 › Security Audit - Authentication & Authorization › should validate JWT tokens properly (9.3s)
  ✓   88 [chromium] › e2e\auth-security.spec.ts:223:7 › Security Audit - Authentication & Authorization › should sanitize username/email in templates (6.7s)
  ✓   86 [chromium] › e2e\auth-security.spec.ts:177:7 › Security Audit - Authentication & Authorization › should enforce two-factor authentication if enabled (7.7s)
  ✓   85 [chromium] › e2e\auth-security.spec.ts:168:7 › Security Audit - Authentication & Authorization › should not accept expired tokens (8.6s)
  ✓   89 [chromium] › e2e\auth-security.spec.ts:238:7 › Security Audit - Authentication & Authorization › should validate request origin for state-changing operations (11.9s)
  ✓   87 [chromium] › e2e\auth-security.spec.ts:193:7 › Security Audit - Authentication & Authorization › should not allow concurrent sessions (15.1s)
  ✓   92 [chromium] › e2e\checkout-and-payment.spec.ts:35:7 › Pricing & Plan Selection › should display three subscription plans (seed, bloom, flourish) (10.3s)
  ✓   93 [chromium] › e2e\checkout-and-payment.spec.ts:56:7 › Pricing & Plan Selection › should display plan details (price, features, duration) (9.6s)
  ✓   94 [chromium] › e2e\checkout-and-payment.spec.ts:73:7 › Pricing & Plan Selection › should allow selecting a plan (seed) (9.2s)
  ✓   91 [chromium] › e2e\checkout-and-payment.spec.ts:21:7 › Pricing & Plan Selection › should display pricing page with subscription plans (11.1s)
  ✓   95 [chromium] › e2e\checkout-and-payment.spec.ts:89:7 › Pricing & Plan Selection › should allow selecting a plan (bloom) (9.6s)
  ✓   96 [chromium] › e2e\checkout-and-payment.spec.ts:105:7 › Pricing & Plan Selection › should allow selecting a plan (flourish) (6.5s)
  ✓   90 [chromium] › e2e\checkout-and-payment.spec.ts:9:7 › Pricing & Plan Selection › should navigate to pricing page from home (16.6s)
  ✓   97 [chromium] › e2e\checkout-and-payment.spec.ts:123:7 › Checkout Process › should require authentication before checkout (7.7s)
  ✓   98 [chromium] › e2e\checkout-and-payment.spec.ts:136:7 › Checkout Process › should redirect unauthenticated users to signin, then checkout works after auth (7.4s)
  ✓   99 [chromium] › e2e\checkout-and-payment.spec.ts:164:7 › Checkout Process › should validate plan parameter in checkout URL (7.8s)
  ✓  100 [chromium] › e2e\checkout-and-payment.spec.ts:179:7 › Checkout Process › should display order summary on checkout (7.9s)
  ✓  101 [chromium] › e2e\checkout-and-payment.spec.ts:192:7 › Checkout Process › should validate required fields before payment (7.4s)
  ✓  102 [chromium] › e2e\checkout-and-payment.spec.ts:208:7 › Checkout Process › should handle checkout with Razorpay payment gateway (7.7s)
  ✓  103 [chromium] › e2e\checkout-and-payment.spec.ts:232:7 › Session Checkout › should navigate to session checkout page (7.0s)
  ✓  104 [chromium] › e2e\checkout-and-payment.spec.ts:250:7 › Session Checkout › should display session details (mentor, time, cost) (5.7s)
  ✓  105 [chromium] › e2e\checkout-and-payment.spec.ts:263:7 › Session Checkout › should display payment form on session checkout (4.7s)
  ✓  109 [chromium] › e2e\dashboard.spec.ts:9:7 › Profile Completion › should navigate to complete profile page after signup (3.0s)
  ✓  107 [chromium] › e2e\checkout-and-payment.spec.ts:296:7 › Timeslot Checkout › should display available time slots in calendar/list format (9.0s)
  ✓  106 [chromium] › e2e\checkout-and-payment.spec.ts:278:7 › Timeslot Checkout › should navigate to timeslot checkout page (9.5s)
  ✓  108 [chromium] › e2e\checkout-and-payment.spec.ts:309:7 › Timeslot Checkout › should allow selecting a time slot (9.0s)
  ✓  114 [chromium] › e2e\dashboard.spec.ts:104:7 › Dashboard Navigation › should navigate to dashboard for authenticated users (7.8s)
  ✓  110 [chromium] › e2e\dashboard.spec.ts:23:7 › Profile Completion › should display profile completion form fields (10.2s)
  ✓  112 [chromium] › e2e\dashboard.spec.ts:58:7 › Profile Completion › should allow filling profile information (9.4s)
  ✓  111 [chromium] › e2e\dashboard.spec.ts:36:7 › Profile Completion › should validate required fields in profile form (10.6s)
  ✓  117 [chromium] › e2e\dashboard.spec.ts:159:7 › Dashboard Sections › should allow viewing diet plans (4.2s)
  ✓  116 [chromium] › e2e\dashboard.spec.ts:145:7 › Dashboard Sections › should display diet plans section (4.4s)
  ✓  118 [chromium] › e2e\dashboard.spec.ts:172:7 › Dashboard Sections › should display mentor section in dashboard (3.1s)
  ✓  113 [chromium] › e2e\dashboard.spec.ts:79:7 › Profile Completion › should submit completed profile form (12.2s)
  ✓  121 [chromium] › e2e\dashboard.spec.ts:216:7 › Session Management › should display scheduled sessions (4.9s)
  ✓  119 [chromium] › e2e\dashboard.spec.ts:186:7 › Dashboard Sections › should display plans/subscription section (7.2s)
  ✓  115 [chromium] › e2e\dashboard.spec.ts:124:7 › Dashboard Navigation › should display dashboard navigation/menu (11.0s)
  ✓  120 [chromium] › e2e\dashboard.spec.ts:200:7 › Dashboard Sections › should display timeslots section (8.2s)
User profile API query time: 10ms
  ✓  129 [chromium] › e2e\database-performance.spec.ts:27:7 › Performance Testing - Database & API Queries › should fetch user profile within time limit (229ms)
  ✓  122 [chromium] › e2e\dashboard.spec.ts:230:7 › Session Management › should display session details (date, time, mentor) (7.2s)
  ✓  123 [chromium] › e2e\dashboard.spec.ts:243:7 › Session Management › should allow canceling a session (7.1s)
  ✘  128 [chromium] › e2e\database-performance.spec.ts:6:7 › Performance Testing - Database & API Queries › should fetch mentors list within time limit (294ms)
Diet plans query time: 17ms
  ✓  131 [chromium] › e2e\database-performance.spec.ts:70:7 › Performance Testing - Database & API Queries › should handle diet plan retrieval efficiently (216ms)
  ✘  130 [chromium] › e2e\database-performance.spec.ts:47:7 › Performance Testing - Database & API Queries › should fetch mentor sessions with pagination efficiently (271ms)
Subscription status query time: 13ms
  ✘  132 [chromium] › e2e\database-performance.spec.ts:90:7 › Performance Testing - Database & API Queries › should process multiple sequential queries efficiently (267ms)
  ✓  133 [chromium] › e2e\database-performance.spec.ts:132:7 › Performance Testing - Database & API Queries › should handle subscription data retrieval efficiently (208ms)
Search query time: 16ms
  ✓  134 [chromium] › e2e\database-performance.spec.ts:197:7 › Performance Testing - Database & API Queries › should handle search queries efficiently (229ms)
Complex filter query time: 16ms
  ✓  135 [chromium] › e2e\database-performance.spec.ts:219:7 › Performance Testing - Database & API Queries › should handle complex filter combinations (211ms)
3 concurrent database writes completed in 28ms
  ✓  136 [chromium] › e2e\database-performance.spec.ts:242:7 › Performance Testing - Database & API Queries › should handle concurrent database writes (307ms)
Analytics dashboard query time: 13ms
  ✓  137 [chromium] › e2e\database-performance.spec.ts:273:7 › Performance Testing - Database & API Queries › should retrieve analytics data efficiently (233ms)
Active sessions query time: 13ms
  ✓  125 [chromium] › e2e\dashboard.spec.ts:272:7 › Account Settings › should display user information on profile (7.3s)
  ✓  138 [chromium] › e2e\database-performance.spec.ts:293:7 › Performance Testing - Database & API Queries › should handle session lookups quickly (272ms)
  ✓  124 [chromium] › e2e\dashboard.spec.ts:258:7 › Account Settings › should navigate to user profile/account settings (8.4s)
Bulk data retrieval (100 records) completed in 14ms
10 concurrent API queries completed in 17ms
  ✓  139 [chromium] › e2e\database-performance.spec.ts:313:7 › Performance Testing - Database & API Queries › should handle bulk data operations (283ms)
  ✓  140 [chromium] › e2e\database-performance.spec.ts:333:7 › Performance Testing - Database & API Queries › should maintain query performance with concurrent requests (264ms)
  ✘  141 [chromium] › e2e\database-performance.spec.ts:357:7 › Performance Testing - Database & API Queries › should measure database connection pool efficiency (288ms)
  ✓  126 [chromium] › e2e\dashboard.spec.ts:286:7 › Account Settings › should allow updating user information (6.2s)
Filtered mentor query time: 52ms
Billing history pagination query time: 33ms
  ✓  127 [chromium] › e2e\dashboard.spec.ts:307:7 › Account Settings › should display subscription info (5.7s)
  ✓  146 [chromium] › e2e\database-performance.spec.ts:112:7 › Performance Testing - Database & API Queries › should handle filtered mentor queries efficiently (423ms)
  ✓  145 [chromium] › e2e\database-performance.spec.ts:152:7 › Performance Testing - Database & API Queries › should handle billing history pagination (458ms)
  ✘  147 [chromium] › e2e\database-performance.spec.ts:174:7 › Performance Testing - Database & API Queries › should cache frequently accessed data (520ms)
  ✘  152 [chromium] › e2e\memory-leak-detection.spec.ts:221:7 › Performance Testing - Memory & Resource Leaks › should handle connection pooling efficiently (405ms)
Memory after form interactions: 0.0% increase
  ✓  149 [chromium] › e2e\memory-leak-detection.spec.ts:150:7 › Performance Testing - Memory & Resource Leaks › should not leak memory with form interactions (8.5s)
Memory after dialog interactions: 0.0% increase
  ✓  150 [chromium] › e2e\memory-leak-detection.spec.ts:185:7 › Performance Testing - Memory & Resource Leaks › should clean up after dialog interactions (12.8s)
Event listeners - Initial: 0, Final: 0
  ✓  151 [chromium] › e2e\memory-leak-detection.spec.ts:72:7 › Performance Testing - Memory & Resource Leaks › should clean up event listeners properly (11.3s)
DOM Nodes - Initial: 173, Final: 173
  ✓  144 [chromium] › e2e\memory-leak-detection.spec.ts:98:7 › Performance Testing - Memory & Resource Leaks › should not have DOM memory leaks (25.1s)
Resources loaded - Initial page: 29, New page: 36
  ✘  143 [chromium] › e2e\memory-leak-detection.spec.ts:38:7 › Performance Testing - Memory & Resource Leaks › should not leak memory during rapid API calls (30.5s)
  ✓  153 [chromium] › e2e\memory-leak-detection.spec.ts:278:7 › Performance Testing - Memory & Resource Leaks › should handle resource cleanup on page unload (21.0s)
Active timers - Initial: 0, Final: 0
  ✓  156 [chromium] › e2e\memory-leak-detection.spec.ts:335:7 › Performance Testing - Memory & Resource Leaks › should handle timer cleanup properly (18.9s)
  ✘  148 [chromium] › e2e\memory-leak-detection.spec.ts:122:7 › Performance Testing - Memory & Resource Leaks › should handle repeated image loading without memory leak (33.6s)
Memory during scroll: 0.0% increase
  ✓  154 [chromium] › e2e\memory-leak-detection.spec.ts:247:7 › Performance Testing - Memory & Resource Leaks › should not leak memory with scroll interactions (24.7s)
  ✘  142 [chromium] › e2e\memory-leak-detection.spec.ts:6:7 › Performance Testing - Memory & Resource Leaks › should not leak memory during page navigation (37.2s)
Memory during rapid state changes: 0.0% increase
  ✓  157 [chromium] › e2e\memory-leak-detection.spec.ts:364:7 › Performance Testing - Memory & Resource Leaks › should not leak memory during rapid state changes (16.7s)
  ✘  155 [chromium] › e2e\memory-leak-detection.spec.ts:298:7 › Performance Testing - Memory & Resource Leaks › should not accumulate garbage during background operations (30.3s)
  ✓  158 [chromium] › e2e\mentor-and-booking.spec.ts:9:7 › Mentor Browsing › should navigate to mentors page from home (14.8s)
  ✓  163 [chromium] › e2e\mentor-and-booking.spec.ts:61:7 › Mentor Browsing › should display mentor profile information (6.7s)
  ✓  161 [chromium] › e2e\mentor-and-booking.spec.ts:47:7 › Mentor Browsing › should view mentor details when clicking on a mentor (15.1s)
  ✓  162 [chromium] › e2e\mentor-and-booking.spec.ts:35:7 › Mentor Browsing › should allow filtering or searching mentors (13.0s)
  ✓  159 [chromium] › e2e\mentor-and-booking.spec.ts:21:7 › Mentor Browsing › should display mentors page with list (17.3s)
  ✓  164 [chromium] › e2e\mentor-and-booking.spec.ts:79:7 › Session Booking Flow › should display available time slots for a mentor (10.1s)
  ✓  166 [chromium] › e2e\mentor-and-booking.spec.ts:130:7 › Session Booking Flow › should display session details on checkout page (5.3s)
  ✓  165 [chromium] › e2e\mentor-and-booking.spec.ts:116:7 › Session Booking Flow › should redirect to checkout when booking a session (7.0s)
  ✓  167 [chromium] › e2e\mentor-and-booking.spec.ts:97:7 › Session Booking Flow › should allow booking a session (7.7s)
  ✓  169 [chromium] › e2e\mentor-and-booking.spec.ts:156:7 › Timeslot Selection › should allow selecting a timeslot (6.0s)
  ✓  170 [chromium] › e2e\payment-security.spec.ts:6:7 › Security Audit - Payment & Sensitive Data › should not expose payment tokens in URLs (5.8s)
  ✓  168 [chromium] › e2e\mentor-and-booking.spec.ts:142:7 › Timeslot Selection › should display available timeslots (7.1s)
  ✓  172 [chromium] › e2e\payment-security.spec.ts:34:7 › Security Audit - Payment & Sensitive Data › should not display full card numbers (5.2s)
  ✓  171 [chromium] › e2e\payment-security.spec.ts:13:7 › Security Audit - Payment & Sensitive Data › should encrypt sensitive payment data (5.4s)
  ✓  173 [chromium] › e2e\payment-security.spec.ts:43:7 › Security Audit - Payment & Sensitive Data › should validate Razorpay integration security (5.1s)
  ✓  174 [chromium] › e2e\payment-security.spec.ts:54:7 › Security Audit - Payment & Sensitive Data › should not expose API secrets (3.1s)
  ✓  175 [chromium] › e2e\payment-security.spec.ts:70:7 › Security Audit - Payment & Sensitive Data › should require HTTPS for payment endpoints (5.1s)
  ✓  176 [chromium] › e2e\payment-security.spec.ts:87:7 › Security Audit - Payment & Sensitive Data › should sanitize payment response data (5.0s)
  ✓  177 [chromium] › e2e\payment-security.spec.ts:104:7 › Security Audit - Payment & Sensitive Data › should prevent payment tampering (5.4s)
  ✓  179 [chromium] › e2e\payment-security.spec.ts:135:7 › Security Audit - Payment & Sensitive Data › should not expose payment IDs in error messages (5.2s)
  ✓  178 [chromium] › e2e\payment-security.spec.ts:124:7 › Security Audit - Payment & Sensitive Data › should not store sensitive payment data in localStorage (5.3s)
  ✓  181 [chromium] › e2e\payment-security.spec.ts:167:7 › Security Audit - Payment & Sensitive Data › should enforce proper CORS for payment APIs (5.4s)
  ✘  160 [chromium] › e2e\memory-leak-detection.spec.ts:396:7 › Performance Testing - Memory & Resource Leaks › should measure peak memory usage (30.3s)
Homepage load time: 3448ms
  ✓  183 [chromium] › e2e\performance.spec.ts:6:7 › Performance Testing - Load & Response Times › should load homepage within acceptable time (3.7s)
Mentors page load time: 3748ms | Cards: 0
  ✓  185 [chromium] › e2e\performance.spec.ts:28:7 › Performance Testing - Load & Response Times › should load mentors page with pagination (4.1s)
  ✓  182 [chromium] › e2e\payment-security.spec.ts:182:7 › Security Audit - Payment & Sensitive Data › should not allow payment without proper authentication (6.3s)
Dashboard load time: 6085ms
  ✓  184 [chromium] › e2e\performance.spec.ts:17:7 › Performance Testing - Load & Response Times › should load dashboard within acceptable time (6.4s)
5 concurrent requests completed in 2497ms
  ✓  186 [chromium] › e2e\performance.spec.ts:44:7 › Performance Testing - Load & Response Times › should handle concurrent API requests (6.5s)
Large list render time: 2017ms
10 form interactions completed in 553ms
  ✓  188 [chromium] › e2e\performance.spec.ts:103:7 › Performance Testing - Load & Response Times › should maintain performance with form interactions (4.5s)
  ✓  187 [chromium] › e2e\performance.spec.ts:71:7 › Performance Testing - Load & Response Times › should render large lists efficiently (6.0s)
Checkout page load time: 7238ms
  ✓  190 [chromium] › e2e\performance.spec.ts:127:7 › Performance Testing - Load & Response Times › should load checkout page within time limit (7.5s)
  ✓  180 [chromium] › e2e\payment-security.spec.ts:152:7 › Security Audit - Payment & Sensitive Data › should validate subscription tampering prevention (16.9s)
Form submission response time: 2139ms
  ✓  195 [chromium] › e2e\performance.spec.ts:230:7 › Performance Testing - Load & Response Times › should handle form submission response time (7.7s)
  ✘  193 [chromium] › e2e\performance.spec.ts:182:7 › Performance Testing - Load & Response Times › should measure Core Web Vitals indicators (9.9s)
  ✘  196 [chromium] › e2e\performance.spec.ts:256:7 › Performance Testing - Load & Response Times › should maintain performance under network latency simulation (6.8s)
3 API calls batched in 2119ms
3 images loaded in 94ms
  ✓  198 [chromium] › e2e\performance.spec.ts:290:7 › Performance Testing - Load & Response Times › should batch process API calls efficiently (7.2s)
  ✓  191 [chromium] › e2e\performance.spec.ts:138:7 › Performance Testing - Load & Response Times › should handle image loading efficiently (17.2s)
5 scroll interactions completed in 669ms
  ✓  192 [chromium] › e2e\performance.spec.ts:161:7 › Performance Testing - Load & Response Times › should respond to scroll interactions quickly (16.7s)
4 page navigations completed in 19004ms
  ✓  189 [chromium] › e2e\performance.spec.ts:86:7 › Performance Testing - Load & Response Times › should handle rapid page navigation (19.5s)
  ✓  204 [chromium] › e2e\security-checks.spec.ts:77:7 › Security Audit - SQL Injection & OWASP › should enforce HTTPS in production (315ms)
  ✓  199 [chromium] › e2e\security-checks.spec.ts:6:7 › Security Audit - SQL Injection & OWASP › should prevent SQL injection in login (4.9s)
  ✓  200 [chromium] › e2e\security-checks.spec.ts:21:7 › Security Audit - SQL Injection & OWASP › should prevent XSS in user profile (5.0s)
Layout responsive test passed
  ✓  197 [chromium] › e2e\performance.spec.ts:272:7 › Performance Testing - Load & Response Times › should render without layout shift (14.3s)
  ✓  203 [chromium] › e2e\security-checks.spec.ts:67:7 › Security Audit - SQL Injection & OWASP › should have security headers (5.1s)
  ✓  205 [chromium] › e2e\security-checks.spec.ts:85:7 › Security Audit - SQL Injection & OWASP › should validate and sanitize form inputs (4.9s)
  ✓  201 [chromium] › e2e\security-checks.spec.ts:35:7 › Security Audit - SQL Injection & OWASP › should prevent CSRF attacks (8.1s)
  ✓  202 [chromium] › e2e\security-checks.spec.ts:54:7 › Security Audit - SQL Injection & OWASP › should not expose sensitive data in DOM (8.2s)
  ✘  194 [chromium] › e2e\performance.spec.ts:210:7 › Performance Testing - Load & Response Times › should handle memory efficiently during navigation (28.3s)
  ✓  209 [chromium] › e2e\security-checks.spec.ts:172:7 › Security Audit - SQL Injection & OWASP › should sanitize error messages (7.5s)
  ✓  210 [chromium] › e2e\security-checks.spec.ts:185:7 › Security Audit - SQL Injection & OWASP › should prevent cookie theft via XSS (7.8s)
  ✓  208 [chromium] › e2e\security-checks.spec.ts:162:7 › Security Audit - SQL Injection & OWASP › should not allow direct parameter tampering in URLs (11.1s)
  ✓  211 [chromium] › e2e\security-checks.spec.ts:203:7 › Security Audit - SQL Injection & OWASP › should validate file uploads (7.4s)
  ✓  212 [chromium] › e2e\security-checks.spec.ts:218:7 › Security Audit - SQL Injection & OWASP › should not expose API endpoints in client code (7.3s)
  ✓  213 [chromium] › e2e\security-checks.spec.ts:243:7 › Security Audit - SQL Injection & OWASP › should prevent clickjacking with X-Frame-Options (5.6s)
  ✓  214 [chromium] › e2e\security-checks.spec.ts:252:7 › Security Audit - SQL Injection & OWASP › should not log sensitive data (5.2s)
  ✓  217 [chromium] › e2e\security-checks.spec.ts:283:7 › Security Audit - SQL Injection & OWASP › should prevent open redirect vulnerabilities (6.4s)
  ✓  216 [chromium] › e2e\security-checks.spec.ts:269:7 › Security Audit - SQL Injection & OWASP › should have Content Security Policy (6.9s)
  ✓  215 [chromium] › e2e\security-checks.spec.ts:227:7 › Security Audit - SQL Injection & OWASP › should implement proper session timeout (7.1s)
  ✓  206 [chromium] › e2e\security-checks.spec.ts:108:7 › Security Audit - SQL Injection & OWASP › should protect against rate limiting bypass (20.2s)
  ✓  219 [chromium] › e2e\security-checks.spec.ts:312:7 › Security Audit - SQL Injection & OWASP › should enforce strong password requirements (4.5s)
  ✓  220 [chromium] › e2e\security-checks.spec.ts:330:7 › Security Audit - SQL Injection & OWASP › should validate email format properly (4.5s)
  ✓  218 [chromium] › e2e\security-checks.spec.ts:295:7 › Security Audit - SQL Injection & OWASP › should sanitize user-generated content (8.9s)
  ✓  207 [chromium] › e2e\security-checks.spec.ts:140:7 › Security Audit - SQL Injection & OWASP › should prevent auth boundary bypass (21.8s)


  1) [chromium] › e2e\api-load-testing.spec.ts:6:7 › Performance Testing - API Load Testing › should handle concurrent checkout API requests 

    Error: expect(received).toBe(expected) // Object.is equality

    Expected: 10
    Received: 0

      30 |     // All requests should succeed
      31 |     const successCount = results.filter((r: any) => !r.error).length;
    > 32 |     expect(successCount).toBe(concurrentRequests);
         |                          ^
      33 |
      34 |     // Should complete within reasonable time
      35 |     expect(totalTime).toBeLessThan(3000);
        at R:\Github\YogVaidya\e2e\api-load-testing.spec.ts:32:26

    attachment #1: screenshot (image/png) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
    test-results\api-load-testing-Performan-57bc1-rrent-checkout-API-requests-chromium\test-failed-1.png
    ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ

  2) [chromium] › e2e\api-load-testing.spec.ts:75:7 › Performance Testing - API Load Testing › should handle mentor search under load 

    Error: expect(received).toBe(expected) // Object.is equality

    Expected: 15
    Received: 0

       96 |     // All searches should succeed
       97 |     const successCount = results.filter((r: any) => !r.error).length;
    >  98 |     expect(successCount).toBe(searches);
          |                          ^
       99 |
      100 |     // Should complete within 2 seconds
      101 |     expect(totalTime).toBeLessThan(2000);
        at R:\Github\YogVaidya\e2e\api-load-testing.spec.ts:98:26

    attachment #1: screenshot (image/png) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
    test-results\api-load-testing-Performan-42125-le-mentor-search-under-load-chromium\test-failed-1.png
    ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ

  3) [chromium] › e2e\api-load-testing.spec.ts:389:7 › Performance Testing - API Load Testing › should measure API response time distribution 

    Error: page.evaluate: TypeError: Failed to execute 'fetch' on 'Window': Failed to parse URL from /api/mentors?limit=10
        at eval (eval at evaluate (:290:30), <anonymous>:2:16)
        at UtilityScript.evaluate (<anonymous>:292:16)
        at UtilityScript.<anonymous> (<anonymous>:1:44)
        at eval (eval at evaluate (:290:30), <anonymous>:2:16)
        at UtilityScript.evaluate (<anonymous>:292:16)
        at UtilityScript.<anonymous> (<anonymous>:1:44)
        at R:\Github\YogVaidya\e2e\api-load-testing.spec.ts:395:18

    attachment #1: screenshot (image/png) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
    test-results\api-load-testing-Performan-04008--response-time-distribution-chromium\test-failed-1.png
    ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ

  4) [chromium] › e2e\api-load-testing.spec.ts:420:7 › Performance Testing - API Load Testing › should handle sustained API load 

    Error: expect(received).toBeGreaterThan(expected)

    Expected: > 5
    Received:   0

      439 |
      440 |     // Should maintain decent throughput
    > 441 |     expect(requestsPerSecond).toBeGreaterThan(5);
          |                               ^
      442 |
      443 |     console.log(`Sustained load test (5s):
      444 |       Total requests: ${requestCount}
        at R:\Github\YogVaidya\e2e\api-load-testing.spec.ts:441:31

    attachment #1: screenshot (image/png) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
    test-results\api-load-testing-Performan-ab12e-d-handle-sustained-API-load-chromium\test-failed-1.png
    ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ

  5) [chromium] › e2e\database-performance.spec.ts:6:7 › Performance Testing - Database & API Queries › should fetch mentors list within time limit 

    Error: expect(received).not.toBeNull()

    Received: null

      20 |     // API should respond within 10 seconds (baseline)
      21 |     expect(queryTime).toBeLessThan(10000);
    > 22 |     expect(data).not.toBeNull();
         |                      ^
      23 |
      24 |     console.log(`Mentors API query time: ${queryTime}ms`);
      25 |   });
        at R:\Github\YogVaidya\e2e\database-performance.spec.ts:22:22

    attachment #1: screenshot (image/png) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
    test-results\database-performance-Perfo-3da26-tors-list-within-time-limit-chromium\test-failed-1.png
    ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ

  6) [chromium] › e2e\database-performance.spec.ts:47:7 › Performance Testing - Database & API Queries › should fetch mentor sessions with pagination efficiently 

    Error: expect(received).not.toBeNull()

    Received: null

      63 |     // Paginated query should complete within reasonable time
      64 |     expect(queryTime).toBeLessThan(10000);
    > 65 |     expect(data).not.toBeNull();
         |                      ^
      66 |
      67 |     console.log(`Mentor sessions paginated query time: ${queryTime}ms`);
      68 |   });
        at R:\Github\YogVaidya\e2e\database-performance.spec.ts:65:22

    attachment #1: screenshot (image/png) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
    test-results\database-performance-Perfo-22956-with-pagination-efficiently-chromium\test-failed-1.png
    ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ

  7) [chromium] › e2e\database-performance.spec.ts:90:7 › Performance Testing - Database & API Queries › should process multiple sequential queries efficiently 

    Error: expect(received).toBeGreaterThan(expected)

    Expected: > 0
    Received:   0

      105 |     // 3 sequential queries should complete within 20 seconds
      106 |     expect(totalTime).toBeLessThan(20000);
    > 107 |     expect(results.length).toBeGreaterThan(0);
          |                            ^
      108 |
      109 |     console.log(`3 sequential database queries completed in ${totalTime}ms`);
      110 |   });
        at R:\Github\YogVaidya\e2e\database-performance.spec.ts:107:28

    attachment #1: screenshot (image/png) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
    test-results\database-performance-Perfo-80b90-uential-queries-efficiently-chromium\test-failed-1.png
    ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ

  8) [chromium] › e2e\database-performance.spec.ts:174:7 › Performance Testing - Database & API Queries › should cache frequently accessed data 

    Error: page.evaluate: TypeError: Failed to execute 'fetch' on 'Window': Failed to parse URL from /api/mentors?limit=10
        at eval (eval at evaluate (:290:30), <anonymous>:2:14)
        at UtilityScript.evaluate (<anonymous>:292:16)
        at UtilityScript.<anonymous> (<anonymous>:1:44)
        at eval (eval at evaluate (:290:30), <anonymous>:2:14)
        at UtilityScript.evaluate (<anonymous>:292:16)
        at UtilityScript.<anonymous> (<anonymous>:1:44)
        at R:\Github\YogVaidya\e2e\database-performance.spec.ts:179:16

    attachment #1: screenshot (image/png) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
    test-results\database-performance-Perfo-659f9-he-frequently-accessed-data-chromium\test-failed-1.png
    ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ

  9) [chromium] › e2e\database-performance.spec.ts:357:7 › Performance Testing - Database & API Queries › should measure database connection pool efficiency 

    Error: page.evaluate: TypeError: Failed to execute 'fetch' on 'Window': Failed to parse URL from /api/users/profile
        at eval (eval at evaluate (:290:30), <anonymous>:2:16)
        at UtilityScript.evaluate (<anonymous>:292:16)
        at UtilityScript.<anonymous> (<anonymous>:1:44)
        at eval (eval at evaluate (:290:30), <anonymous>:2:16)
        at UtilityScript.evaluate (<anonymous>:292:16)
        at UtilityScript.<anonymous> (<anonymous>:1:44)
        at R:\Github\YogVaidya\e2e\database-performance.spec.ts:362:18

    attachment #1: screenshot (image/png) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
    test-results\database-performance-Perfo-a89b6--connection-pool-efficiency-chromium\test-failed-1.png
    ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ

  10) [chromium] › e2e\memory-leak-detection.spec.ts:6:7 › Performance Testing - Memory & Resource Leaks › should not leak memory during page navigation 

    Test timeout of 30000ms exceeded.

    Error: page.goto: Test timeout of 30000ms exceeded.
    Call log:
      - navigating to "http://localhost:3000/", waiting until "load"


      21 |     for (let i = 0; i < 10; i++) {
      22 |       await page.goto(`${BASE_URL}/mentors`);
    > 23 |       await page.goto(`${BASE_URL}/`);
         |                  ^
      24 |       await page.waitForTimeout(100);
      25 |     }
      26 |
        at R:\Github\YogVaidya\e2e\memory-leak-detection.spec.ts:23:18

    Error Context: test-results\memory-leak-detection-Perf-1371f-mory-during-page-navigation-chromium\error-context.md

  11) [chromium] › e2e\memory-leak-detection.spec.ts:38:7 › Performance Testing - Memory & Resource Leaks › should not leak memory during rapid API calls 

    Test timeout of 30000ms exceeded.

    Error: page.evaluate: Test timeout of 30000ms exceeded.

      53 |     // Make rapid API calls
      54 |     for (let i = 0; i < 20; i++) {
    > 55 |       await page.evaluate(async () => {
         |                  ^
      56 |         return fetch("/api/mentors?limit=10", { method: "GET" })
      57 |           .then((r) => r.json())
      58 |           .catch(() => ({}));
        at R:\Github\YogVaidya\e2e\memory-leak-detection.spec.ts:55:18

    attachment #1: screenshot (image/png) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
    test-results\memory-leak-detection-Perf-31f16-mory-during-rapid-API-calls-chromium\test-failed-1.png
    ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ

    Error Context: test-results\memory-leak-detection-Perf-31f16-mory-during-rapid-API-calls-chromium\error-context.md

  12) [chromium] › e2e\memory-leak-detection.spec.ts:122:7 › Performance Testing - Memory & Resource Leaks › should handle repeated image loading without memory leak 

    Test timeout of 30000ms exceeded.

    Error: page.goto: Test timeout of 30000ms exceeded.
    Call log:
      - navigating to "http://localhost:3000/mentors", waiting until "load"


      135 |     // Load mentor page multiple times (has images)
      136 |     for (let i = 0; i < 5; i++) {
    > 137 |       await page.goto(`${BASE_URL}/mentors`);
          |                  ^
      138 |       await page.waitForTimeout(200);
      139 |     }
      140 |
        at R:\Github\YogVaidya\e2e\memory-leak-detection.spec.ts:137:18

    attachment #1: screenshot (image/png) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
    test-results\memory-leak-detection-Perf-3c60a-loading-without-memory-leak-chromium\test-failed-1.png
    ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ

    Error Context: test-results\memory-leak-detection-Perf-3c60a-loading-without-memory-leak-chromium\error-context.md

  13) [chromium] › e2e\memory-leak-detection.spec.ts:221:7 › Performance Testing - Memory & Resource Leaks › should handle connection pooling efficiently 

    Error: page.evaluate: TypeError: Failed to execute 'fetch' on 'Window': Failed to parse URL from /api/mentors
        at eval (eval at evaluate (:290:30), <anonymous>:2:16)
        at UtilityScript.evaluate (<anonymous>:292:16)
        at UtilityScript.<anonymous> (<anonymous>:1:44)
        at eval (eval at evaluate (:290:30), <anonymous>:2:16)
        at UtilityScript.evaluate (<anonymous>:292:16)
        at UtilityScript.<anonymous> (<anonymous>:1:44)
        at R:\Github\YogVaidya\e2e\memory-leak-detection.spec.ts:226:18

    attachment #1: screenshot (image/png) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
    test-results\memory-leak-detection-Perf-42e5b-nection-pooling-efficiently-chromium\test-failed-1.png
    ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ

  14) [chromium] › e2e\memory-leak-detection.spec.ts:298:7 › Performance Testing - Memory & Resource Leaks › should not accumulate garbage during background operations 

    Test timeout of 30000ms exceeded.

    Error: page.evaluate: Test timeout of 30000ms exceeded.

      312 |     // Trigger multiple background operations
      313 |     for (let i = 0; i < 10; i++) {
    > 314 |       await page.evaluate(async () => {
          |                  ^
      315 |         // Simulate background fetch
      316 |         return fetch("/api/mentors?limit=5", { method: "GET" })
      317 |           .then((r) => r.json())
        at R:\Github\YogVaidya\e2e\memory-leak-detection.spec.ts:314:18

    attachment #1: screenshot (image/png) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
    test-results\memory-leak-detection-Perf-18a21-uring-background-operations-chromium\test-failed-1.png
    ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ

    Error Context: test-results\memory-leak-detection-Perf-18a21-uring-background-operations-chromium\error-context.md

  15) [chromium] › e2e\memory-leak-detection.spec.ts:396:7 › Performance Testing - Memory & Resource Leaks › should measure peak memory usage 

    Test timeout of 30000ms exceeded.

    Error: page.evaluate: Test timeout of 30000ms exceeded.

      410 |
      411 |       // Perform operations
    > 412 |       await page.evaluate(async () => {
          |                  ^
      413 |         return fetch("/api/mentors", { method: "GET" })
      414 |           .then((r) => r.json())
      415 |           .catch(() => ({}));
        at R:\Github\YogVaidya\e2e\memory-leak-detection.spec.ts:412:18

    attachment #1: screenshot (image/png) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
    test-results\memory-leak-detection-Perf-d73f0-d-measure-peak-memory-usage-chromium\test-failed-1.png
    ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ

    Error Context: test-results\memory-leak-detection-Perf-d73f0-d-measure-peak-memory-usage-chromium\error-context.md

  16) [chromium] › e2e\performance.spec.ts:182:7 › Performance Testing - Load & Response Times › should measure Core Web Vitals indicators 

    Error: expect(received).toBeLessThan(expected)

    Expected: < 1800
    Received:   3348

      200 |
      201 |     // FCP should be under 1.8 seconds (Good threshold)
    > 202 |     expect(metrics.firstContentfulPaint).toBeLessThan(1800);
          |                                          ^
      203 |
      204 |     // DOM interactive should be under 3 seconds
      205 |     expect(metrics.domInteractive).toBeLessThan(3000);
        at R:\Github\YogVaidya\e2e\performance.spec.ts:202:42

    attachment #1: screenshot (image/png) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
    test-results\performance-Performance-Te-b0585--Core-Web-Vitals-indicators-chromium\test-failed-1.png
    ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ

    Error Context: test-results\performance-Performance-Te-b0585--Core-Web-Vitals-indicators-chromium\error-context.md

  17) [chromium] › e2e\performance.spec.ts:210:7 › Performance Testing - Load & Response Times › should handle memory efficiently during navigation 

    Error: expect(received).toBeLessThan(expected)

    Expected: < 3000
    Received:   7638

      223 |
      224 |     // Final navigation should still be fast
    > 225 |     expect(finalLoadTime).toBeLessThan(3000);
          |                           ^
      226 |
      227 |     console.log(`Final page load after multiple navigations: ${finalLoadTime}ms`);
      228 |   });
        at R:\Github\YogVaidya\e2e\performance.spec.ts:225:27

    attachment #1: screenshot (image/png) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
    test-results\performance-Performance-Te-53501-ficiently-during-navigation-chromium\test-failed-1.png
    ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ

    Error Context: test-results\performance-Performance-Te-53501-ficiently-during-navigation-chromium\error-context.md

  18) [chromium] › e2e\performance.spec.ts:256:7 › Performance Testing - Load & Response Times › should maintain performance under network latency simulation 

    Error: expect(received).toBeLessThan(expected)

    Expected: < 5000
    Received:   6257

      265 |
      266 |     // Should still load reasonably fast even with latency
    > 267 |     expect(throttledLoadTime).toBeLessThan(5000);
          |                               ^
      268 |
      269 |     console.log(`Throttled page load time: ${throttledLoadTime}ms`);
      270 |   });
        at R:\Github\YogVaidya\e2e\performance.spec.ts:267:31

    attachment #1: screenshot (image/png) ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
    test-results\performance-Performance-Te-327b3--network-latency-simulation-chromium\test-failed-1.png
    ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ

    Error Context: test-results\performance-Performance-Te-327b3--network-latency-simulation-chromium\error-context.md

  18 failed
    [chromium] › e2e\api-load-testing.spec.ts:6:7 › Performance Testing - API Load Testing › should handle concurrent checkout API requests 
    [chromium] › e2e\api-load-testing.spec.ts:75:7 › Performance Testing - API Load Testing › should handle mentor search under load 
    [chromium] › e2e\api-load-testing.spec.ts:389:7 › Performance Testing - API Load Testing › should measure API response time distribution 
    [chromium] › e2e\api-load-testing.spec.ts:420:7 › Performance Testing - API Load Testing › should handle sustained API load 
    [chromium] › e2e\database-performance.spec.ts:6:7 › Performance Testing - Database & API Queries › should fetch mentors list within time limit 
    [chromium] › e2e\database-performance.spec.ts:47:7 › Performance Testing - Database & API Queries › should fetch mentor sessions with pagination efficiently 
    [chromium] › e2e\database-performance.spec.ts:90:7 › Performance Testing - Database & API Queries › should process multiple sequential queries efficiently 
    [chromium] › e2e\database-performance.spec.ts:174:7 › Performance Testing - Database & API Queries › should cache frequently accessed data 
    [chromium] › e2e\database-performance.spec.ts:357:7 › Performance Testing - Database & API Queries › should measure database connection pool efficiency 
    [chromium] › e2e\memory-leak-detection.spec.ts:6:7 › Performance Testing - Memory & Resource Leaks › should not leak memory during page navigation 
    [chromium] › e2e\memory-leak-detection.spec.ts:38:7 › Performance Testing - Memory & Resource Leaks › should not leak memory during rapid API calls 
    [chromium] › e2e\memory-leak-detection.spec.ts:122:7 › Performance Testing - Memory & Resource Leaks › should handle repeated image loading without memory leak 
    [chromium] › e2e\memory-leak-detection.spec.ts:221:7 › Performance Testing - Memory & Resource Leaks › should handle connection pooling efficiently 
    [chromium] › e2e\memory-leak-detection.spec.ts:298:7 › Performance Testing - Memory & Resource Leaks › should not accumulate garbage during background operations 
    [chromium] › e2e\memory-leak-detection.spec.ts:396:7 › Performance Testing - Memory & Resource Leaks › should measure peak memory usage 
    [chromium] › e2e\performance.spec.ts:182:7 › Performance Testing - Load & Response Times › should measure Core Web Vitals indicators 
    [chromium] › e2e\performance.spec.ts:210:7 › Performance Testing - Load & Response Times › should handle memory efficiently during navigation 
    [chromium] › e2e\performance.spec.ts:256:7 › Performance Testing - Load & Response Times › should maintain performance under network latency simulation 
  202 passed (3.8m)