Skip to main content
Testlio Testing Coverages

Testing coverages that Testlio offers.

Doris Sooläte avatar
Written by Doris Sooläte
Updated over a year ago
  • Analytics testing: Analytics Testing at Testlio involves verifying that streaming applications and web sites are outputting the correct data when different events take place within the applications and web sites.

  • API testing: is an end-point testing for input/output consistency and performance. While API testing is often automated, manual testing is typically done through tools such as Postman and SoapUI.

  • App testing: Mobile application testing is a type of testing where the software developed especially for a mobile device is tested for its usability and functionality.

  • Beta testing: Beta testing is considered the last stage of testing, and it involves distributing the product to beta test sites and real users with the goal to detect any issues before the public release.

  • Build testing: Build testing focuses on software application’s package verification. Scenarios include installations, upgrades and downgrades on different environments and devices.

  • Content testing: Content testing involves tracking content and product usage for compliance and more. For instance - is relevant content - such as media, documents, etc - available at the right time for relevant users in relevant regions.

  • Design testing: During design testing, software concepts and prototypes that are often delivered in PDFs or mock environments are validated against user expectations.

  • Device testing: Device testing, often referred to as device compatibility testing, focuses on the application’s compatibility, suitability on unique hardware/OS combinations.

  • Functional testing: Functional testing is conducted to ensure that the application meets all the specified requirements, all its features are responsive, and it serves the end-user as expected. Identifying who the target end-users are and which purpose the application serves are prerequisites for any type of functional testing. Read more here.

  • Localization testing: Localization Testing is verifying that translations of content are correct and that no User Interface (UI) layout issue is created. Read more here.

  • Location testing: Location testing happens in-field situations (cities, parks, stadiums, stores, trains, etc.).

  • Payments testing: Payments testing focuses on real financial transaction flows done by real payment instruments. Read more here.

  • Production testing: Production Testing focuses on already released and available software experiences. Often this is done to gain additional confidence in released software behavior in real conditions or for validating flows which are unavailable in testing environments.

  • Regression testing: Regression Testing is defined as a type of software testing to confirm that a recent program or code change has not adversely affected existing features. Regression Testing is nothing but a full or partial selection of already executed test plans which are re-executed to ensure existing functionalities work fine.

  • Role testing: Role testing focuses on coverage of products with multiple key user types (e.g. buyer and seller).

  • Setup testing: Setup testing focuses on software offerings with multiple configuration options - e.g. where initial or ongoing configuration drives key differences on how software behaves and which functionality is available to the end users.

  • Stream testing: Livestream testing is the process of testing live broadcasts, such as sporting events, TV premieres, and more. Read more here.

  • Voice testing: Voice testing includes audio command response systems coverage (such as smart home assistants).

  • Web testing: Device testing, often referred to as device compatibility testing, focuses on the application’s compatibility, suitability on unique hardware/OS combinations.

Did this answer your question?