Prompt library

Important:

This feature is currently part of an audit process and is not to be considered part of the FedRAMP Authorization until the review is finalized. See here the full list of features currently under review.

A prompt library is a collection of both predefined and custom prompts, that you can use when offering additional instructions to Autopilot^TM.

Prerequisites

To view and use the prompt library, your Test Manager role must have the Autopilot Prompt permission set to Read. If you want to create, update, or delete prompts, then your Test Manager role must have the Autopilot Prompt permission set to either Create, Update, or Delete.

Predefined prompts

To help you get started with using AI-powered capabilities, you can use the predefined prompts from the prompt library. You can also update them, according to your needs.

End-to-End Flow Verification

• Description: Guidelines for generating end-to-end tests from flow diagrams.
• Mode of use: Create tests from requirement.
• Prompt:

  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.

Rapid Test Idea Generation

• Description: Guidelines for generating numerous ideas for testing quickly.
• Mode of use: Create tests from requirement.
• Prompt:

  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.

Valid E2E Scenario Testing

• Description: Guidelines for generating tests for valid end-to-end scenarios only.
• Mode of use: Create tests from requirement.
• Prompt:

  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.

Elusive issue detection

• Description: Guidelines for generating tests to find elusive issues.
• Mode of use: Create tests from requirement.
• Prompt:

  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.

Boundary-Value Testing

• Description: Guidelines for generating tests focused on boundary-value testing.
• Mode of use: Create tests from requirement.
• Prompt:

  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.

SAP business process testing

• Description: Guidelines for generating SAP business test cases.
• Mode of use: Create tests from SAP transaction.
• Prompt:

  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.

Performance Evaluation

• Description: Guidelines for analyzing requirements for performance-related aspects
• Mode of use: Evaluate requirement quality.
• Prompt:

  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.

Security Assessment

• Description: Guidelines for analyzing requirements for security-related aspects
• Mode of use: Evaluate requirement quality.
• Prompt:

  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.

Multifaceted Audit

• Description: Guidelines for analyzing requirements from many different perspectives.
• Mode of use: Evaluate requirement quality.
• Prompt:

  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.

Adding a custom prompt

Before you create a custom prompt, visit the best practices for the available AI-powered capabilities:

• Generate tests for requirements
• Quality-check requirements

Steps

To create a custom prompt:

1. Navigate to Project Settings, and then to Prompt library.
2. Select Add prompt and start configuring the prompt:
   1. Name: The name of the prompt.
   2. Description: A description about what the prompt does.
   3. Mode of use:: For what AI-capability is designed for:
      1. Create tests from requirement
      2. Create tests from SAP transaction
      3. Evaluate requirement quality
   4. Prompt: The instructions that Autopilot^TM should follow.
3. Select Create to confirm changes.

Managing prompts

As part of managing prompts, you can update, clone, or delete them.

Updating prompts

To update either a predefined or custom prompt:

1. Select the name of the desired prompt.
2. Start changing the Description, Mode of use, or Prompt.
3. Select Save to confirm changes.

Cloning prompts

To clone a prompt:

1. For the desired prompt, select More Options.
2. Select Clone.
3. (Optional) Update any of the prompt fields, such as Name, Description, Mode of use, or Prompt.
4. Select Create to apply your changes.

Deleting prompts

To delete prompts:

1. For the desired prompt, select More Options.
2. Select Delete.

   The prompt is permanently deleted.