QoEtient

Information Hub

• What is QoEtient 2.0?

  QoEtient 2.0 is an AI-based, true no-code automated test executor that can read and understand test cases written in natural language. It can automate tests on compatible devices, provide regular test results, and offer AI-generated insights on test failures. QoEtient 2.0 is not a full test automation framework but a no-code executor library that can be integrated into existing test automation systems.
  

• How does QoEtient 2.0 differ from traditional script-based automation?

  Unlike traditional script-based automation, which requires programming skills and constant maintenance, QoEtient 2.0 uses natural language test cases. This eliminates the need for coding knowledge and reduces maintenance efforts, as QoEtient 2.0 can adapt to changes in the application without manual intervention.
  

• What are the four stages of QoEtient 2.0's operation?

  The four stages are: 1) Understanding the App under test, 2) Understanding the Test Case, 3) Executing the Test Case, and 4) Providing test outcomes. These stages involve describing the app, interpreting natural language test cases, executing tests, and delivering comprehensive results.
  

• How can QoEtient 2.0 be integrated into existing test automation systems?

  QoEtient 2.0 can be integrated by connecting integration points, including instructing SE on how to view and control specific device types, connecting SE's test results to existing reporting systems, and using QoEtient 2.0's interfaces to start it with necessary information like test cases, app details, and device information.
  

• What are Device Control Adapters in QoEtient 2.0?

  Device Control Adapters are implementations of interfaces defined within QoEtient 2.0 that allow it to interact with various devices and applications. These adapters enable QoEtient 2.0 to access, view, and control different device types without direct dependencies on third-party libraries.
  

• How does QoEtient 2.0 handle reporting?

  QoEtient 2.0 generates events during test execution containing detailed information about the test's progress. Interested parties can subscribe to these events and access detailed report data. This approach allows QoEtient 2.0 to remain decoupled from specific reporting systems while enabling data consumption by various reporting mechanisms.
  

• How does QoEtient 2.0's licensing work?

  Each QoEtient 2.0 license permits the creation of one QoEtient 2.0 instance, which can run one test case on one device at a time. Multiple licenses allow for parallel test execution across multiple devices. The licensing system is integrated within the QoEtient 2.0 library and controls instance initialization based on available licenses.
  

• Are there any cloud costs associated with using QoEtient 2.0?

  Yes, QoEtient 2.0 integrates with generative AI APIs hosted in the AWS cloud, resulting in minimal charges for each execution. The exact costs depend on the complexity of the test case and whether instruction regeneration is required.
  

• Can QoEtient 2.0 detect issues beyond the primary objective of a test case?

  Yes, QoEtient 2.0 has human-like abilities to note down anomalies or bugs while testing another test case, even if they are not the primary objective of that test.
  

• How does QoEtient 2.0 compare to no-code automation systems?

  While no-code automation systems use pre-coded blocks that users assemble visually, QoEtient 2.0 is a true no-code solution. It eliminates the need for block assembly by directly interpreting natural language test cases, making it more efficient and resilient to changes in the application.
  

• How does QoEtient 2.0 understand the app under test?

  During the initial onboarding stage, users provide QoEtient 2.0 with a description of the app in natural language, following a specified format. This description includes details about each screen, functionalities, unique identifiers, and navigation options. A typical app description contains about 500 lines of natural language information, representing the app's screens and functionalities.
  

• What kind of test outcomes does QoEtient 2.0 provide?

  QoEtient 2.0 provides real-time feedback on test execution progress, reporting outcomes for each test step. It delivers a clear verdict (pass, fail, or could not test) for each test case. Additionally, QoEtient 2.0 offers a comprehensive summary of the execution, including noteworthy observations and potential issues that might require further investigation.
  

• How does QoEtient 2.0 adapt to changes in the application being tested?

  QoEtient 2.0's true no-code approach allows it to adapt to changes in the application without manual intervention. By interpreting natural language test cases and cross-referencing them with the app description, QoEtient 2.0 can adjust its execution strategy automatically when the application evolves, reducing the need for test maintenance.
  

• Can QoEtient 2.0 work with different types of devices and platforms?

  Yes, QoEtient 2.0 is designed to work with various device types and platforms. Using Device Control Adapters, QoEtient 2.0 can interact with different devices such as Android phones, iPhones, browsers, and set-top boxes. These adapters allow QoEtient 2.0 to view and control specific device types without being directly dependent on device-specific libraries.
  

• How does QoEtient 2.0 contribute to reducing the cost and effort associated with test maintenance?

  QoEtient 2.0 significantly reduces test maintenance costs and efforts by eliminating the need for coding or assembling pre-coded blocks. Its ability to understand and execute natural language test cases, coupled with its adaptability to application changes, means that users spend less time updating and maintaining test cases. This results in a more efficient and cost-effective testing process.