Prompt library

Verify each unique path in the flow diagram as a separate test case.

Focus exclusively on testing end-to-end paths within the diagram.

Ensure each test case represents a complete journey from the starting to an endpoint.

Achieve comprehensive coverage by testing every complete journey within the diagram.

Do not create any test steps, only test case titles.

Limit the test case titles to a maximum of 12 words.

Create a minimum of 50 creative test cases.

Create test cases exclusively for valid, complete user journeys.

Avoid test cases for invalid input or field validations.

Keep test case titles under 6 words, ensuring they are clear and informative.

Generate only unconventional yet plausible test scenarios to reveal hidden issues.

Focus on test scenarios often missed in standard tests, requiring deeper insight.

Challenge system design and user behavior assumptions to find weaknesses.

Use a wide range of user behaviors, including atypical ones, to uncover issues.

Define valid ranges and identify minimum, maximum, and edge values for each input.

Focus test cases on these boundary values, including just inside and outside valid ranges.

Cover lowest, highest, and subdivided range limits in your test cases.

Ensure all input field boundaries across the application are tested.

Focus on valid and realistic SAP business scenarios.

Provide example values for all mandatory fields. Use realistic values derived from master data or configuration tables.

For optional fields, include a note indicating they can be skipped unless specified.

Avoid edge test cases and invalid inputs.

Create top 5 most common used test cases.

Generate the top 10 enhancement suggestions focusing solely on performance aspects:

-Time: Check if specific response times under various load conditions are detailed.

-Throughput: Check if expected throughput rates are clearly specified.

-Scalability: Check if the requirement addresses scalability under increasing loads.

-Resource Usage: Check if limits on CPU, memory, and storage usage are defined.

-Efficiency: Check if the requirement promotes efficient use of resources.

-Load Handling: Check if strategies for handling peak load conditions are included.

-Concurrency: Check if behaviors under concurrent user scenarios are specified.

-Latency: Check if maximum acceptable latency figures are clearly stated.

Generate the top 10 enhancement suggestions focusing solely on security aspects:

-Access: Check if it is clear who can access the application and under what conditions.

-Protection: Check if encryption, anonymization & secure storage measures are defined.

-Authentication: Check if identity verification and permissions controls are included.

-Vulnerability: Check if measures against known vulnerabilities are addressed.

-Transmission: Check if encrypted data transmissions are mandated.

-Logging: Check if detailed logging and monitoring provisions are included.

-Compliance: Check if adherence to relevant security standards is ensured.

-Errors: Check if secure error handling practices are specified.

Generate the top 10 enhancement suggestions from diverse perspectives:

-User Flow: Check for detailed information about the user flow and application logic.

-Consistency: Examine for logical coherence and lack of contradictions.

-Relevance: Check if the requirement clearly highlights the needs of the user.

-Rationale: Check if it explains why it is necessary and what problem it solves.

-Clarity: Check for precision and clarity in the requirement description.

-Criteria: Check for measurable and achievable acceptance criteria.

-Completeness: Check for inclusion of all critical functionalities.

-Prerequisites: Note missing prerequisites or conditions needed before implementation.