DocQ
Last updated
Last updated
DocQ is an intelligent question-answering bot specifically designed to provide accurate and detailed answers to questions related to Qyrus testing platform. Whenever you need any assistance related to the features available in Qyrus, DocQ will help you with that. It is developed to ensure that users can quickly find the information they need about Qyrus product.
DocQ provides answers to only the questions found in our user documentation for each service.
Currently DocQ supports Web, Mobile, QAPI, Device Farm, Desktop Testing and data testing services.
User can ask any question related to these services with DocQ to get the relevant answer.
Step 1: Log in to DocQ using your application URL, email, and password.
Step 2: Once you have successfully logged in, you will land into main page of DocQ where you can ask questions to it. There are also ready-made example questions available that you can click on to start a conversation with the bot.
As mentioned earlier DocQ supports 6 services right now.
Web Testing You can ask DocQ any questions or explore available features related to 'web testing.'
For example:
Steps to parameterize tests in web
What is encapsulate and how to use that in web service?
What is visual testing and what is the use of it in web?
I have an locator issue. Is there any feature that can help me to solve locator issue?
Mobile Testing Ask DocQ any questions related to 'mobile testing.'
For example:
How schedules work in mobility?
What are all update screen option available in mobility?
What are the launch action types available in mobility?
What are all integrations does mobility support?
QAPI Ask DocQ questions related to 'QAPI'
For example:
How to test APIs?
what is scheduling in QAPI?
Which APIs we can import?
How to generate testcases using NOVA in QAPI?
what is playground?
Device Farm Ask questions to DocQ related to 'Device Farm'
For example:
How to create project in device farm?
what are all the file types we can upload in device farm?
what is difference between automatic testing and manual testing in device farm?
Desktop Testing User can even ask questions related to 'desktop testing' with DocQ
For example:
What is desktop testing?
What is QloudBridge app?
What is parameterization in desktop testing?
Data Testing Similarly users can even ask questions related to 'data testing' service with DocQ
For example:
What is data testing
What are different types of jobs in data testing?
What are the inputs user need to provide for the database connection?
If no relevant data is found in the document, the user will receive the response: "Couldn't find any relevant information! Please contact support@qyrus.com for more info."
If DocQ is not completely certain about the information, it will begin the response with: "I don't know the exact information about this, but here is some related information." In this case, you should continue reading the response.