Test cases: Expected User Behavior / Results

The purpose of these test cases is to ensure that the product behaves correctly under various user interactions and scenarios, providing accurate, reliable, and user-friendly experiences. Each test case specifies actions that a user might take, the expected outcome, and the steps our engineering team can take to validate that the system performs as intended.

Hash Tags

• Description: Test how Analyst handles the use of hashtags within user prompts. The system should recognize and appropriately process hashtags to influence the context or focus of the analysis. Hash tags are formed from the token/project id in the database.

• Testing: Enter prompts containing single or multiple hashtags related to crypto topics. Verify that the hashtags guide the analysis in the expected direction, influencing the content returned by the agent.

Using multiple different Hash Tags in the same Session

• Description: Test the Analyst's ability to handle multiple hashtags within a single session. The agent should be able to manage and prioritize multiple hashtags, producing an analysis that reflects the combined context.

• Testing: Input prompts with multiple hashtags in a single session. Observe and confirm that the analysis includes aspects of all provided hashtags, without any being ignored or overly prioritized.

Returning to and Resuming a Session

• Description: Ensure that users can return to a previously active session and seamlessly resume where they left off, with all prior context preserved.

• Testing: Start a session, leave it inactive for a specified period, and then return to it. Verify that the session resumes with all previous content and context intact, allowing for continuous interaction.

Prompting Analyst to summarize all session content

• Description: Test the functionality where users can request a summary of all content generated during a session. The summary should concisely encapsulate the key points and findings.

• Testing: Conduct a session with multiple interactions and then prompt the agent for a summary. Ensure that the summary accurately reflects the content covered during the session.

Create a Preset

• Description: Validate the process of creating a Preset prompt that can be used repeatedly for specific analyses. The preset should save correctly and be easily accessible for future sessions.

• Testing: Create a preset with a defined prompt and confirm that it saves correctly. Use the preset in subsequent sessions to verify that it functions as expected.

Input multiple URLs into a prompt

• Description: Ensure that Analyst can handle multiple URLs inputted into a single prompt. The agent should analyze the content of all URLs and incorporate the relevant information into the response.

• Testing: Input multiple URLs in a prompt and verify that the analysis includes relevant details from all provided sources, with no information missing or incorrectly prioritized.

Analysis Deletion

• Description: Test the functionality that allows users to delete previously generated analyses. The deletion should be straightforward and permanently remove the content from the session.

• Testing: Generate an analysis, delete it, and confirm that it is no longer accessible in the session. Attempt to retrieve the deleted analysis to ensure it is permanently removed.

Follow-up Conversation

• Description: Validate that users can initiate follow-up conversations based on previous analyses. The follow-up should build on the prior context and provide deeper insights or additional information.

• Testing: Conduct an analysis, then prompt the agent for a follow-up. Ensure that the agent accurately references the previous conversation and provides relevant extended analysis.

Editing an Analysis

• Description: Test the ability for users to edit a previously generated analysis. The edited content should reflect the changes made and update the session accordingly.

• Testing: Generate an analysis, make edits to it, and confirm that the changes are reflected in the session history and that subsequent interactions acknowledge the edits.

Editing a Plan

• Description: Ensure that users can edit a saved plan or preset within the system. The edits should be saved correctly, and the updated plan should function as intended in future sessions.

• Testing: Create a plan, edit it, and verify that the changes are saved. Use the edited plan in subsequent sessions to ensure it works as expected.

Public Posting

• Description: Validate the functionality that allows users to post session results or summaries publicly. The content should be shared correctly and be accessible via the intended public platform by other users.

• Testing: Complete a session and post the results publicly. Verify that the post is visible on the selected platform and that it accurately reflects the content of the session.

Private Posting

• Description: Test the system’s capability to allow users to post session results or summaries privately. The content should be shared with specified individuals or groups without public access.

• Testing: Complete a session and post the results privately. Confirm that the content is only accessible to the intended recipients and that it is not publicly visible.