-
Notifications
You must be signed in to change notification settings - Fork 17
Qase integration and ios test setup #12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
tobi-legan
wants to merge
13
commits into
tetherto:main
Choose a base branch
from
tobi-legan:qase-integration-and-ios-test-setup
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Qase integration and ios test setup #12
tobi-legan
wants to merge
13
commits into
tetherto:main
from
tobi-legan:qase-integration-and-ios-test-setup
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Introduced E2E testing framework in the `e2e` directory, including configuration files and test scripts. - Added `HomeOnboardingScreen` page object for managing onboarding screen interactions. - Implemented initial test for wallet app onboarding, verifying UI elements and welcome messages. - Updated `.gitignore` to exclude E2E test artifacts and configuration files. - Modified `app.json` to disable development client for production builds. - Added `package-lock.json` and `package.json` for E2E testing dependencies.
… multi-platform config support - Add Qase.io test management integration - Create platform-specific WebdriverIO configs (iOS/Android) - Implement qase() wrapper for automatic test result reporting - Add platform detection for test run naming ([iOS]/[Android]) - Support both iOS and Android e2e testing - Update README with platform-specific test commands
jonathunne
requested changes
Dec 5, 2025
Contributor
|
@tobi-legan , aside from the comments above - I agree with @ignaciolarranaga 's comment on #11 that this (and #11) doesn't need to be a seperate project with new package.json |
- Added configuration files for E2E testing in the `test/e2e` directory. - Created `HomeOnboardingScreen` page object for managing onboarding interactions. - Developed initial test for wallet app onboarding, verifying UI elements and welcome messages. - Updated `package.json` and `package-lock.json` to include necessary dependencies for testing. - Modified `.gitignore` to exclude test artifacts and configuration files. - Removed legacy E2E testing setup from `e2e` directory.
- Added `dotenv`, `qase-api-client`, and `strip-ansi` to `package.json` and `package-lock.json`. - Updated test specifications path in `wdio.base.conf.ts` to point to the new structure. - Removed legacy `wdio.conf.ts` file. - Adjusted TypeScript configuration to exclude `node_modules` and `e2e` directories.
- Replace all 'any' types with proper TypeScript types (WebdriverIO.Capabilities, Record<string, unknown>, etc.) - Fix Android APK path in wdio.android.conf.ts (test/apps/app-release.apk) - Fix Android test script in package.json to use wdio.android.conf.ts - Add missing driver import in home-onboarding-screen.ts - All tests passing on both iOS and Android
- Updated `package.json` to reference new test configuration files for E2E testing. - Added `wdio.conf.ts` for Android E2E testing setup. - Added `wdio.ios.conf.ts` for iOS E2E testing setup, including specific capabilities for both platforms.
…os.conf.ts to test/
- Modified `package.json` to point to the correct paths for E2E testing scripts. - Added `wdio.base.conf.ts` for shared WebdriverIO configuration across platforms. - Introduced `wdio.android.conf.ts` for Android-specific WebdriverIO settings, including capabilities and app path.
jonathunne
previously approved these changes
Dec 11, 2025
stefannikolic
approved these changes
Dec 11, 2025
itsdeka
previously approved these changes
Dec 16, 2025
The merge-base changed after approval.
jonathunne
approved these changes
Dec 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds Qase.io test management integration for e2e tests, enabling automatic test result reporting with platform-specific test run naming. It also introduces separate WebdriverIO configurations for iOS and Android platforms, making it easier to run and manage platform-specific tests.
Key additions:
qase-wrapper.ts) that provides aqase()function for wrapping test caseswdio.base.conf.ts,wdio.ios.conf.ts,wdio.android.conf.tstest:ios,test:android,test:allMotivation and Context
This change is required to:
The problem this solves: Previously, there was no way to automatically track test results in a centralized test management system, and running tests for different platforms required manual configuration changes.
Related Issue
PR fixes the following issue: N/A (New feature implementation - no existing issue)
Type of change
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update