Question 1

What is AutomationTekAI?

Accepted Answer

AutomationTekAI is an AI-assisted test-case generation tool that helps QA professionals convert requirements, user stories and acceptance criteria into structured testing scenarios.

Question 2

Who can use AutomationTekAI?

Accepted Answer

AutomationTekAI is designed for manual testers, automation engineers, QA leads, developers, business analysts, product owners and software teams involved in quality assurance.

Question 3

Do I need automation experience?

Accepted Answer

No. You can use AutomationTekAI to create structured manual test scenarios without writing automation code. Optional Playwright, Selenium and Cypress starter exports are available for teams that want a starting point for automation.

Question 4

Does AutomationTekAI replace QA engineers?

Accepted Answer

No. AutomationTekAI supports QA professionals by accelerating test design and identifying useful scenarios. Generated results should always be reviewed against the application’s requirements and business rules.

Question 5

Can I try AutomationTekAI for free?

Accepted Answer

Yes. The current free trial allows 5 generations or 3 days, whichever comes first. Sign in with Google to start from the Generate workflow.

Question 6

What information should I provide?

Accepted Answer

For better results, provide a clear user story, acceptance criteria, business rules, user roles, validation rules, dependencies and relevant examples. Avoid passwords, tokens and confidential customer data.

Question 7

What types of test scenarios can AutomationTekAI generate?

Accepted Answer

Depending on your selected testing mode and input, the application can generate structured scenarios such as functional, UI, API, negative and edge cases. Advanced and risk-based modes are available according to your plan.

Question 8

Can I generate test cases from a Jira story?

Accepted Answer

Yes. When Jira access is configured, you can provide supported issue keys and AutomationTekAI will fetch the ticket content. You can also copy the relevant user story and acceptance criteria from Jira and paste them into the text workflow.

Question 9

Can I edit generated test cases?

Accepted Answer

Generated cases are currently shown as a read-only draft with expand and copy actions. Review them in the UI, then copy or export them into your team’s test-management process for any edits.

Question 10

Can I export generated test cases?

Accepted Answer

Yes. Current export options include PDF, Markdown, CSV (including the Excel download button, which currently produces CSV), and a Jira Test Issue CSV format. Some export options require Pro access.

Question 11

Does AutomationTekAI generate automation code?

Accepted Answer

Yes. In addition to structured test cases, AutomationTekAI can produce Playwright (TypeScript), Selenium (Java) and Cypress starter scripts. These are skeleton starting points and still need selectors, fixtures, data and assertions before they are production-ready. Automation export is a Pro feature.

Question 12

How can I generate more complete test cases?

Accepted Answer

Include complete acceptance criteria, user roles, validations, sample input, expected output, error conditions, dependencies and platform requirements.

Question 13

Are AI-generated test cases always correct?

Accepted Answer

No. AI-generated results may miss application-specific rules or misunderstand incomplete requirements. All generated scenarios should be reviewed before being used for release validation.

Question 14

What happens if my requirement is incomplete?

Accepted Answer

The generated output may include assumptions or may not cover important business conditions. Users should provide complete acceptance criteria and verify every assumption.

Question 15

Why are some generated scenarios too generic?

Accepted Answer

Generic results are usually caused by broad or incomplete input. Add specific business rules, field validations, user roles, test data examples and expected behaviour.

Question 16

Can AutomationTekAI guarantee complete test coverage?

Accepted Answer

No tool can guarantee complete coverage from requirements alone. Coverage depends on requirement quality, system knowledge, architecture, integrations and professional QA review.

Question 17

Should I directly automate every generated test case?

Accepted Answer

No. Review, prioritize and stabilize the scenarios first. Automate cases that are repeatable, valuable and suitable for regression testing.

Question 18

Should I enter passwords or production credentials?

Accepted Answer

No. Never enter passwords, access tokens, API keys, production credentials or confidential customer information into a test-case generation request.

Question 19

Should I enter personal customer data?

Accepted Answer

No. Use anonymized or synthetic test data instead of personally identifiable or confidential customer information.

Question 20

What is included in the free plan?

Accepted Answer

The free trial includes limited generation (5 generations or 3 days, whichever comes first), Basic testing mode, limited Advanced mode access, and email or community support. Risk-based testing, automation export, project history and some export options are Pro features.

Question 21

What is included in the paid plan?

Accepted Answer

Pro unlocks unlimited generations, Advanced and Risk-Based modes, automation starter exports, project save and history, coverage gap analysis, priority support and additional export options. Pricing is shown in the Pricing tab and currently starts at ₹499/month for India or about $4.99/month for international checkout, with other regional currencies where available.

Question 22

Can a complete QA team use one account?

Accepted Answer

Do not share login credentials. Each person should use an individual Google account. Dedicated team workspaces are not available yet and may be considered as a future feature.

Question 23

Why did test-case generation fail?

Accepted Answer

Generation may fail because of a temporary connection problem, an incomplete request or a service issue. Retry once, simplify the input and contact support if the problem continues.

Question 24

Why is generation taking longer than expected?

Accepted Answer

Complex requirements and temporary service demand can increase processing time. Avoid submitting the same request repeatedly while a generation is still running.

Question 25

Why did I receive duplicate scenarios?

Accepted Answer

Similar or repeated requirements can produce overlapping scenarios. Review the input for duplication and remove repeated acceptance criteria before regenerating.

Question 26

Why are expected results unclear?

Accepted Answer

Add explicit expected behaviour, validation messages, user roles and business rules to the input.

Question 27

How can I report a problem?

Accepted Answer

Email automationtekaisupport@gmail.com with the workflow you used, the displayed error message and non-sensitive context. Do not send passwords, tokens or confidential customer data.

What is AutomationTekAI?+

Who can use AutomationTekAI?+

Do I need automation experience?+

Does AutomationTekAI replace QA engineers?+

Can I try AutomationTekAI for free?+

What information should I provide?+

What types of test scenarios can AutomationTekAI generate?+

Can I generate test cases from a Jira story?+

Can I edit generated test cases?+

Can I export generated test cases?+

Does AutomationTekAI generate automation code?+

How can I generate more complete test cases?+

Are AI-generated test cases always correct?+

What happens if my requirement is incomplete?+

Why are some generated scenarios too generic?+

Can AutomationTekAI guarantee complete test coverage?+

Should I directly automate every generated test case?+

Should I enter passwords or production credentials?+

Should I enter personal customer data?+

Is my information stored?+

Is my data used to train AI models?+

Can I delete my projects or generated data?+

What is included in the free plan?+

What is included in the paid plan?+

Can I cancel my subscription?+

Can a complete QA team use one account?+

Why did test-case generation fail?+

Why is generation taking longer than expected?+

Why did I receive duplicate scenarios?+

Why are expected results unclear?+

Which browsers are supported?+

How can I report a problem?+