mirror of
https://github.com/mattermost/mattermost-mobile.git
synced 2026-11-07 11:20:12 +00:00
Closes manual release-test gaps for mobile (Detox + Maestro), automating new test cases and hardening flaky/CI-only failures uncovered along the way. ### New coverage automated - **MM-T416** offline/online post-retry (Android via airplane mode; iOS ultimately marked unsupported — see below) - **MM-T1194 / MM-T1193** custom ToS accept/decline survives relaunch - **MM-T3251** status change via account UI (cross-user visibility) - **MM-T510** channel-wide/keyword mention delivery — later expanded to a full 5-channel mention matrix with exact server-side counts - **MM-T3261 (_1/_2)** Report a Problem external hand-off (browser link mode, email mode) - **MM-T2940** iOS managed-config (MDM) pre-fill/autoconnect - **MM-T3271/3272** opening the app from a push notification (synthetic notification payloads, background/closed states) - Un-skipped several tests that turned out to already pass (stale skips) ### Root-caused failing tests - **Android SQLite corruption**: traced to native Kotlin DB connections not opening in WAL mode while JSI did (post #10109) — journal-mode mismatch corrupted the store on push-triggered writes. Fixed properly with a **WAL patch** (#10117) rather than the original destructive "wipe app database" workaround, which was reverted. - **Fabric crash** (`addViewAt`/reparent) on `SlideUpPanelItem` taps — root-caused to view flattening racing sheet mounts; fixed with `collapsable={false}` (went through a revert/re-revert once CI reproduced the crash without it). - **Search race**: stale in-flight search results could overwrite a cleared search box — fixed with request-id tagging. - **iOS offline detection**: multiple iterations (AAAA sampling → Cloudflare-prefix check → final decision) landed on refusing iOS offline simulation outright, since all E2E servers are Cloudflare-fronted/anycast and the address space can't be enumerated/blocked. - **MM-T3261 config patch** intermittently silently ignored by the server — root-caused to `ReportAProblemType` being environment-managed on PR Spinwicks (config PATCH returns 200 but is silently dropped); now detected and reported as a skip with proven cause, not a failure. - **MM-T416 failed-post timing**: multiple rounds of tightening the wait bound to match the client's actual retry/backoff/timeout ceiling (ended at ~150s, derived from OkHttp/retry-interceptor math, not guessed). - **MM-T5603 upload wait**: raised to match the client's real 180s upload timeout. - **Classification banner suite**: fixed to verify config state directly instead of trusting a PATCH reply that the cloud sometimes drops. ### CI/reporting infra fixes - Dedicated Maestro steps (MM-T3261, MM-T67856_4) weren't feeding into the merged JUnit report and couldn't gate pass/fail — fixed report merging/naming so they now count. - Android Maestro logcat capture added (previously iOS-only diagnostics). - Jest retry logic no longer discards passing results from a shard killed by timeout. - Sharding raised 24→28. - Removed dead Detox Pilot/Playbooks scaffolding (unused, uncovered by CI). ### Cleanup - Comment/docs pass stripping narrative session-archaeology from long explanatory comments, keeping only load-bearing facts and CI references.
45 lines
1.6 KiB
JavaScript
45 lines
1.6 KiB
JavaScript
// Copyright (c) 2015-present Mattermost, Inc. All Rights Reserved.
|
|
// See LICENSE.txt for license information.
|
|
|
|
const assert = require('node:assert/strict');
|
|
const {describe, it} = require('node:test');
|
|
|
|
const {isRetriableCloudWarmupError} = require('./retriable_cloud_error');
|
|
|
|
describe('isRetriableCloudWarmupError', () => {
|
|
it('should retry 403 from an inactive Matterwick API', () => {
|
|
assert.equal(isRetriableCloudWarmupError({status: 403, message: 'Request failed with status code 403'}), true);
|
|
});
|
|
|
|
it('should retry a redirect to the inactive portal even when status is 302', () => {
|
|
assert.equal(isRetriableCloudWarmupError({
|
|
status: 302,
|
|
message: '[seed] Test server redirected to cloud/inactive',
|
|
}), true);
|
|
});
|
|
|
|
it('should retry HTML from the inactive portal on a 200', () => {
|
|
assert.equal(isRetriableCloudWarmupError({
|
|
status: 200,
|
|
body: '<!DOCTYPE html>\n<html lang="en">',
|
|
}), true);
|
|
});
|
|
|
|
it('should retry 5xx and missing status', () => {
|
|
assert.equal(isRetriableCloudWarmupError({status: 502, message: 'Bad Gateway'}), true);
|
|
assert.equal(isRetriableCloudWarmupError({message: 'ECONNRESET'}), true);
|
|
});
|
|
|
|
it('should retry 429', () => {
|
|
assert.equal(isRetriableCloudWarmupError({status: 429, message: 'Too Many Requests'}), true);
|
|
});
|
|
|
|
it('should not retry a normal 401 from a live login endpoint', () => {
|
|
assert.equal(isRetriableCloudWarmupError({
|
|
status: 401,
|
|
message: 'Login failed',
|
|
body: {id: 'api.user.login.invalid_credentials'},
|
|
}), false);
|
|
});
|
|
});
|