CI/CD

---

We leverage Continuous Integration/Continuous Delivery (CI/CD) tools to automate the building, testing, and deployment phases of our software development lifecycle. This ensures rapid and reliable delivery of new features and updates.

Our system seamlessly integrates with popular CI/CD platforms, including Jenkins, Bitrise, and GitLab CI/CD, enabling:

• Automated testing triggered by code commits.
• Continuous deployment to staging/production environments.
• Real-time feedback on build status and test results.

By embedding Testmore into your pipeline, you accelerate development velocity while maintaining high code quality.

---

Initiate automated tests via a simple API call. Example request:

POST {{base_url}}/api/triggerRunSet  
Content-Type: application/json  

{
  "monitoringID": "your_monitoring_id",  
  "appURL": "https://your-cdn.com/apps/your-app.ipa",  
  "apiKey": "your_api_key",  
  "credentials": {  
    "username": "username",  
    "password": "password"  
  }  
}

---

Key Fields

Field	Purpose
monitoringID	Unique ID for your test configuration in Testmore.
appURL	Direct link to your app binary (IPA/APK).
apiKey	Authenticates requests to Testmore (store as a secret).
credentials	Optional: Only required if appURL requires HTTP authentication.

---

About Credentials

• 🔒 Not your Testmore login – These credentials are exclusively used to access password-protected appURL binaries.
• Example: If your app is hosted at:
  https://your-cdn.com/apps/your-app.ipa
  and requires login, provide the download credentials in the request.

---

Best Practices

1. Secure secrets: Store apiKey and credentials in your CI/CD tool’s secret manager.
2. Pre-validate URLs: Ensure appURL is accessible before triggering tests.
3. Monitor responses: Check API responses for success/failure status codes.