Best Practices

Token Utility

Overview

Here are the essential best practices for effectively utilizing TestVista to maximize productivity and efficiency:

AI-Generated Quality of File Types: For optimal results, use files in the following order of preference: Word documents, images, and then Excel spreadsheets.

Language Consistency: Ensure that the content of the file is in a single language to avoid confusion and enhance clarity. Currently, English is the best language for processing.

File Organization: Organize topics within the file in a logical order with clear headings from top to bottom. This structure facilitates easy navigation and understanding. If the document includes clear headers and is written with explicit preconditions in the 'given...when...then' format, TestVista can generate higher-quality test cases.

Document Length: Avoid uploading overly lengthy documents or those with numerous requirements. Such documents can result in the generation of hundreds of test cases, which may be difficult to manage.

If your document includes many functions or screens, consider splitting it into smaller documents. Each smaller document should focus on a single screen or a few functions, especially if the screen contains many components that require test cases.
If a screen has a large number of components that need test cases, you should divide the document so that each smaller section focuses on a manageable number of components.

DOs and DON'Ts

Guideline Type	✅ DOs	❌ DON'Ts
Input File	TestVista supports word, excel and image documents. Word format has the best generation quality.	Upload old format files such as .doc, .xls
Input Language	Ensure the document is written in a single language for the best results.	Mix multiple languages in one document.
Document Organization	Structure the document logically with clear headings and organized sections.	Use scattered or ambiguous formatting without clear structure.
	Provide sufficient context for AI to understand the requirement	Assume AI is magic and can understand domain knowledge
	Format requirements using structured frameworks like Given...When...Then such as User Story or Use Case	Use freeform or inconsistent requirement descriptions.
Input File Size	Keep files small and focused on one screen or feature. Input requirement < 10 pages works best.	Upload excessively large documents covering unrelated features.
Document Organization	Review and proofread the document to ensure there are no errors or inconsistencies.	Upload documents with typos, incomplete sentences, or unclear formatting.
AI guidance	Use detailed and explicit descriptions for complex requirements with many components.	Test the AI with overly complex requirement without explicit instructions.
AI guidance	For example: "Help me create test cases for all 20 components on login screen."
Probabilistic nature	Due to the probabilistic nature of AI generation, users can create different test suites and try regenerating the test cases of the uploaded document if the initial test cases do not meet quality expectations.	Rely solely on the first set of generated test cases without exploring different test suites or attempting regenerations to improve test quality and coverage.

On this page

Overview DOs and DON'Ts