mirror of
https://github.com/langgenius/dify.git
synced 2026-07-15 01:17:04 +08:00
d0ea5a5e0d
Co-authored-by: Joel <iamjoel007@gmail.com> Co-authored-by: zyssyz123 <916125788@qq.com> Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com> Co-authored-by: 林玮 (Jade Lin) <linw1995@icloud.com> Co-authored-by: 盐粒 Yanli <mail@yanli.one>
62 lines
3.9 KiB
Gherkin
62 lines
3.9 KiB
Gherkin
@agent-v2 @authenticated @agent-edit
|
|
Feature: Agent v2 Agent Edit page
|
|
@core @stable-model @full-config-agent
|
|
Scenario: Saved orchestration sections are visible on the Agent Edit page
|
|
Given I am signed in as the default E2E admin
|
|
And the Agent Builder stable chat model is available
|
|
And the Agent Builder preseeded Agent "E2E New Agent Builder Full Config" is available
|
|
And the Agent Builder preseeded Agent "E2E New Agent Builder Full Config" includes the core fixture configuration
|
|
When I open the preseeded Agent v2 configure page for "E2E New Agent Builder Full Config" from the Agent Roster
|
|
Then I should see the Agent v2 full-config fixture sections
|
|
|
|
@core @stable-model @full-config-agent
|
|
Scenario: Duplicated Agent inherits configuration without changing the original Agent
|
|
Given I am signed in as the default E2E admin
|
|
And the Agent Builder stable chat model is available
|
|
And the Agent Builder preseeded Agent "E2E New Agent Builder Full Config" is available
|
|
And the Agent Builder preseeded Agent "E2E New Agent Builder Full Config" includes the core fixture configuration
|
|
When I duplicate the preseeded Agent v2 "E2E New Agent Builder Full Config" from the Agent Roster
|
|
Then the duplicated Agent v2 should inherit the full-config fixture from "E2E New Agent Builder Full Config"
|
|
When I open the Agent v2 configure page
|
|
And I fill the Agent v2 prompt editor with the updated E2E prompt
|
|
Then the Agent v2 configuration should be saved automatically
|
|
And the normal Agent v2 draft should use the updated E2E prompt
|
|
And the preseeded Agent v2 "E2E New Agent Builder Full Config" should still use the normal E2E prompt
|
|
|
|
@core @tool-states-agent
|
|
Scenario: Tool states are visible on the Agent Edit page
|
|
Given I am signed in as the default E2E admin
|
|
And the Agent Builder preseeded Agent "E2E New Agent Builder Tool States" is available
|
|
And the Agent Builder preseeded Agent "E2E New Agent Builder Tool States" includes the tool state fixture configuration
|
|
When I open the preseeded Agent v2 configure page for "E2E New Agent Builder Tool States" from the Agent Roster
|
|
Then I should see the Agent v2 tool state fixture tools
|
|
|
|
@tool-error-state @tool-states-agent @feature-gated
|
|
Scenario: Tool credential error states are visible on the Agent Edit page
|
|
Given I am signed in as the default E2E admin
|
|
And Agent v2 Tool credential error state is available
|
|
And the Agent Builder preseeded Agent "E2E New Agent Builder Tool States" is available
|
|
And the Agent Builder preseeded Agent "E2E New Agent Builder Tool States" includes the tool state fixture configuration
|
|
When I open the preseeded Agent v2 configure page for "E2E New Agent Builder Tool States" from the Agent Roster
|
|
Then Agent v2 Tool credential error state should be available
|
|
|
|
@core @dual-retrieval-fixture
|
|
Scenario: Dual Knowledge Retrieval settings are visible on the Agent Edit page
|
|
Given I am signed in as the default E2E admin
|
|
And the Agent Builder preseeded Agent "E2E Agent With Dual Retrieval" is available
|
|
And the Agent Builder preseeded Agent "E2E Agent With Dual Retrieval" includes the dual retrieval fixture configuration
|
|
When I open the preseeded Agent v2 configure page for "E2E Agent With Dual Retrieval" from the Agent Roster
|
|
Then I should see the Agent v2 dual retrieval fixture settings
|
|
|
|
@core @stable-model
|
|
Scenario: Agent Edit opens the same Agent in Agent Console
|
|
Given I am signed in as the default E2E admin
|
|
And the Agent Builder stable chat model is available
|
|
And a workflow app with an Agent v2 node has been created via API
|
|
When I open the app from the app list
|
|
And I open the Agent v2 workflow node panel
|
|
And I open the Agent v2 workflow Agent details
|
|
Then I should see the Agent v2 workflow Agent details for the created Agent
|
|
When I open the Agent v2 workflow Agent in Agent Console
|
|
Then the Agent v2 Agent Console should open for the same workflow Agent
|