Skip to content

Release Tests

Asharam Seervi edited this page Apr 18, 2023 · 11 revisions

Attention: We have migrated our documentation to our new platform, Ant Media Resources. Please follow this link for the latest and up-to-date documentation.

Ant Media Server is continuously tested in different levels and periods.

Test Levels:

  • Unit & Component tests: Run on CI/CD environment automatically for each commit
  • Integration tests: Run on CI/CD environment automatically for each commit
  • Cluster tests: Run on CI/CD environment automatically for each commit
  • Release tests: Partially automatic and intersect with other test levels. Some tests are manual for now but will be automatized.

In this document we tell the release tests that are made on release candidates before releasing the formal version.

Release Tests

Startup & Graceful Shutdown Test

This is for testing server startup and shutdown scenarios. This is performed in Integration tests automatically.

Upgraded Libraries Test

This is is for testing the capabilities of the upgraded 3rd party libraries or running environment (like Tomcat, Java, OS etc) in new release. This test performed in Integration tests automatically.

Performance Tests (Partially automatic)

These test are performed to determine the following metrics:

  • Maximum number of the parallel WebRTC streams on 4 core machine
  • Maximum number of the parallel WebRTC viewers on 4 core machine
  • High load tests: these are performed in 3 months periods and reported with Blog Posts. These test have been made for 10K, 30K and 70K viewers so far.

SDK Tests (Manual)

These tests are performed to check compatibility of the SDKs with the new release. These test are made for Android SDK, iOS SDK and JS SDK+sample pages.

Tests on Change Logs

Normally all newly implemented features have their own Unit or/and Integration tests which are run automatically on each commit. Besides we manually test new features manually on running server. Documentation, UI/UX are also checked with this tests.

Backward Compatibility Tests (manual for now)

This test is made to check backward compatibility of the server. It is expected that if new release is installed on the previous one, all settings are kept and server should continue to run without any problem. This test performed with the following steps:

  • Install previous version
  • Enable SSL
  • Login
  • Add adaptive setting to LiveApp
  • Add License key
  • Install new version on it
  • Check adaptive setting is kept
  • Check SSL is kept
  • Check License Key is kept
  • Repeat installation test for cluster mode

User Guide

Reference

Troubleshooting

Draft

Proposals

Clone this wiki locally