Skip to content

Commit 159e8ae

Browse files
committed
fixed flaky tests & /tools
1 parent f6b8d4e commit 159e8ae

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

tests/e2e/features/skills.feature

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ Feature: Agent skills tests
1212
@SkillsConfig @skip
1313
Scenario: Skill tools are registered when skills are configured
1414
Given The service uses the lightspeed-stack-skills.yaml configuration
15+
And MCP toolgroups are reset for a new MCP configuration
1516
And The service is restarted
1617
When I access REST API endpoint "tools" using HTTP GET method
1718
Then The status code of the response is 200
@@ -132,6 +133,7 @@ Feature: Agent skills tests
132133

133134
Scenario: Skill tools are not registered when no skills are configured
134135
Given The service uses the lightspeed-stack.yaml configuration
136+
And MCP toolgroups are reset for a new MCP configuration
135137
And The service is restarted
136138
When I access REST API endpoint "tools" using HTTP GET method
137139
Then The status code of the response is 200
@@ -644,7 +646,7 @@ Feature: Agent skills tests
644646

645647
# --- Full progressive disclosure flow ---
646648

647-
@SkillsConfig
649+
@SkillsConfig @flaky
648650
Scenario: LLM completes list_skills then load_skill then read_skill_resource via query endpoint
649651
Given The service uses the lightspeed-stack-skills.yaml configuration
650652
And The service is restarted
@@ -703,7 +705,7 @@ Feature: Agent skills tests
703705
"""
704706

705707

706-
@SkillsConfig
708+
@SkillsConfig @flaky
707709
Scenario: LLM completes list_skills then load_skill then read_skill_resource via streaming_query endpoint
708710
Given The service uses the lightspeed-stack-skills.yaml configuration
709711
And The service is restarted

0 commit comments

Comments
 (0)