LCORE-1472: update wording in features (lightspeed-core#1599)

* LCORE-1472: update wording in features

remove duplicated config

---------

Co-authored-by: Radovan Fuchs <rfuchs@rfuchs-thinkpadp1gen7.tpb.csb>

Author: radofuchs

tests/e2e/configuration/library-mode/lightspeed-stack-no-mcp.yaml

@@ -28,6 +28,6 @@ Feature: FAISS support tests
     {"query": "What is the title of the article from Paul?", "system_prompt": "You are an assistant. Always use the file_search tool to answer. Write only lowercase letters", "model": "{MODEL}", "provider": "{PROVIDER}"}
     """
      Then The status code of the response is 200
-      And The response should contain following fragments
+      And The response contains following fragments
           | Fragments in LLM response |
           | great work                |

tests/e2e/configuration/server-mode/lightspeed-stack-no-mcp.yaml

@@ -28,18 +28,18 @@ Feature: Inline RAG (BYOK) support tests
     {"query": "What is the title of the article from Paul?", "system_prompt": "You are an assistant. Write only lowercase letters", "model": "{MODEL}", "provider": "{PROVIDER}"}
     """
     Then The status code of the response is 200
-     And The response should contain following fragments
+     And The response contains following fragments
          | Fragments in LLM response |
          | great work                |
-     And The response should contain non-empty rag_chunks
+     And The response contains non-empty rag_chunks
 
   Scenario: Inline RAG query includes referenced documents
     When I use "query" to ask question with authorization header
     """
     {"query": "What does Paul Graham say about great work?", "model": "{MODEL}", "provider": "{PROVIDER}"}
     """
     Then The status code of the response is 200
-     And The response should contain non-empty referenced_documents
+     And The response contains non-empty referenced_documents
 
   Scenario: Streaming query with inline RAG returns relevant content
     When I use "streaming_query" to ask question with authorization header
@@ -48,7 +48,7 @@ Feature: Inline RAG (BYOK) support tests
     """
     Then The status code of the response is 200
      And I wait for the response to be completed
-     And The streamed response should contain following fragments
+     And The streamed response contains following fragments
          | Fragments in LLM response |
          | great work                |
 
@@ -58,7 +58,7 @@ Feature: Inline RAG (BYOK) support tests
     {"input": "What is the title of the article from Paul?", "model": "{PROVIDER}/{MODEL}", "stream": false, "instructions": "You are an assistant. Write only lowercase letters"}
     """
     Then The status code of the response is 200
-     And The response should contain following fragments
+     And The response contains following fragments
          | Fragments in LLM response |
          | great work                |
 

tests/e2e/features/faiss.feature

@@ -31,10 +31,10 @@ Feature: MCP tests
     {"query": "Say hello", "model": "{MODEL}", "provider": "{PROVIDER}"}
     """
     Then The status code of the response is 200
-    And The response should contain following fragments
+    And The response contains following fragments
         | Fragments in LLM response |
         | Hello                     |
-    And The token metrics should have increased
+    And The token metrics have increased
 
   @MCPFileAuthConfig @flaky
   Scenario: Check if streaming_query endpoint succeeds when MCP file-based auth token is passed
@@ -49,10 +49,10 @@ Feature: MCP tests
     """
     When I wait for the response to be completed
     Then The status code of the response is 200
-    And The streamed response should contain following fragments
+    And The streamed response contains following fragments
         | Fragments in LLM response |
         | Hello                     |
-    And The token metrics should have increased
+    And The token metrics have increased
 
 # File-based (invalid token) — lightspeed-stack-invalid-mcp-file-auth.yaml
   @InvalidMCPFileAuthConfig
@@ -138,10 +138,10 @@ Feature: MCP tests
     {"query": "Say hello", "model": "{MODEL}", "provider": "{PROVIDER}"}
     """
     Then The status code of the response is 200
-    And The response should contain following fragments
+    And The response contains following fragments
         | Fragments in LLM response |
         | Hello                     |
-    And The token metrics should have increased
+    And The token metrics have increased
 
   @MCPKubernetesAuthConfig @flaky
   Scenario: Check if streaming_query endpoint succeeds when MCP kubernetes auth token is passed
@@ -156,10 +156,10 @@ Feature: MCP tests
     """
     When I wait for the response to be completed
     Then The status code of the response is 200
-    And The streamed response should contain following fragments
+    And The streamed response contains following fragments
         | Fragments in LLM response |
         | Hello                     |
-    And The token metrics should have increased
+    And The token metrics have increased
 
   @MCPKubernetesAuthConfig
   Scenario: Check if tools endpoint reports error when MCP kubernetes invalid auth token is passed
@@ -250,10 +250,10 @@ Feature: MCP tests
     {"query": "Say hello", "model": "{MODEL}", "provider": "{PROVIDER}"}
     """
     Then The status code of the response is 200
-    And The response should contain following fragments
+    And The response contains following fragments
         | Fragments in LLM response |
         | Hello                     |
-    And The token metrics should have increased
+    And The token metrics have increased
 
   @MCPClientAuthConfig @flaky
   Scenario: Check if streaming_query endpoint succeeds when MCP client-provided auth token is passed
@@ -271,10 +271,10 @@ Feature: MCP tests
     """
     When I wait for the response to be completed
     Then The status code of the response is 200
-    And The streamed response should contain following fragments
+    And The streamed response contains following fragments
         | Fragments in LLM response |
         | Hello                     |
-    And The token metrics should have increased
+    And The token metrics have increased
 
   @MCPClientAuthConfig
   Scenario: Check if tools endpoint succeeds by skipping when MCP client-provided auth token is omitted
@@ -297,10 +297,10 @@ Feature: MCP tests
     """
     Then The status code of the response is 200
     And The body of the response does not contain mcp-client
-    And The response should contain following fragments
+    And The response contains following fragments
         | Fragments in LLM response |
         | Hello                     |
-    And The token metrics should have increased
+    And The token metrics have increased
 
   @MCPClientAuthConfig @flaky
   Scenario: Check if streaming_query endpoint succeeds by skipping when MCP client-provided auth token is omitted
@@ -315,10 +315,10 @@ Feature: MCP tests
     When I wait for the response to be completed
     Then The status code of the response is 200
     And The body of the response does not contain mcp-client
-    And The streamed response should contain following fragments
+    And The streamed response contains following fragments
         | Fragments in LLM response |
         | Hello                     |
-    And The token metrics should have increased
+    And The token metrics have increased
 
   @MCPClientAuthConfig
   Scenario: Check if tools endpoint reports error when MCP client-provided invalid auth token is passed
@@ -418,10 +418,10 @@ Feature: MCP tests
     {"query": "Say hello", "model": "{MODEL}", "provider": "{PROVIDER}"}
     """
     Then The status code of the response is 200
-    And The response should contain following fragments
+    And The response contains following fragments
         | Fragments in LLM response |
         | Hello                     |
-    And The token metrics should have increased
+    And The token metrics have increased
 
   @MCPOAuthAuthConfig @flaky
   Scenario: Check if streaming_query endpoint succeeds when MCP OAuth auth token is passed
@@ -439,10 +439,10 @@ Feature: MCP tests
     """
     When I wait for the response to be completed
     Then The status code of the response is 200
-    And The streamed response should contain following fragments
+    And The streamed response contains following fragments
         | Fragments in LLM response |
         | Hello                     |
-    And The token metrics should have increased
+    And The token metrics have increased
 
   @MCPOAuthAuthConfig
   Scenario: Check if tools endpoint reports error when MCP OAuth requires authentication

tests/e2e/features/inline_rag.feature

@@ -9,7 +9,8 @@ Feature: MCP Server API tests without configured MCP servers
       And The system is in default state
       And REST API service prefix is /v1
       And the Lightspeed stack configuration directory is "tests/e2e/configuration"
-      And The service uses the lightspeed-stack-no-mcp.yaml configuration
+      And I set the Authorization header to Bearer mcp-e2e-no-config-token
+      And The service uses the lightspeed-stack-no-cache.yaml configuration
       And The service is restarted
 
   Scenario: List MCP servers returns empty list when none configured

tests/e2e/features/mcp.feature

@@ -16,18 +16,18 @@ Feature: Models endpoint tests
      When I access REST API endpoint "models" using HTTP GET method
      Then The status code of the response is 200
       And The body of the response has proper model structure
-      And The models list should not be empty
+      And The models list is not empty
 
   Scenario: Check if models can be filtered
     Given The system is in default state
      When I retrieve list of available models with type set to "llm"
      Then The status code of the response is 200
       And The body of the response has proper model structure
-      And The models list should not be empty
-      And The models list should contain only models of type "llm"
+      And The models list is not empty
+      And The models list contains only models of type "llm"
 
   Scenario: Check if filtering can return empty list of models
     Given The system is in default state
      When I retrieve list of available models with type set to "xyzzy"
      Then The status code of the response is 200
-      And The models list should be empty
+      And The models list is empty

tests/e2e/features/mcp_servers_api_no_config.feature

@@ -18,10 +18,10 @@ Feature: Query endpoint API tests
     {"query": "Generate sample yaml file for simple GitHub Actions workflow.", "system_prompt": "refuse to answer anything but openshift questions", "model": "{MODEL}", "provider": "{PROVIDER}"}
     """
      Then The status code of the response is 200
-      And The response should contain following fragments
+      And The response contains following fragments
           | Fragments in LLM response |
           | ask                       |
-      And The token metrics should have increased
+      And The token metrics have increased
 
   @flaky
   Scenario: Check if LLM responds properly to non-restrictive system prompt to sent question with different system prompt
@@ -31,11 +31,11 @@ Feature: Query endpoint API tests
     {"query": "Generate sample yaml file for simple GitHub Actions workflow.", "system_prompt": "you are linguistic assistant", "model": "{MODEL}", "provider": "{PROVIDER}"}
     """
     Then The status code of the response is 200
-      And The response should contain following fragments
+      And The response contains following fragments
           | Fragments in LLM response |
           | checkout                  |
-      And The response should contain token counter fields
-      And The token metrics should have increased
+      And The response contains token counter fields
+      And The token metrics have increased
 
   #enable on demand
   @skip 
@@ -51,7 +51,7 @@ Feature: Query endpoint API tests
     {"query": "Write a simple code for reversing string", "system_prompt": "provide coding assistance", "model": "{MODEL}", "provider": "{PROVIDER}"}
     """
     Then The status code of the response is 200
-     And The response should contain following fragments
+     And The response contains following fragments
           | Fragments in LLM response |
           | ask                       |
 
@@ -63,7 +63,7 @@ Feature: Query endpoint API tests
      """
       Then The status code of the response is 404
       And The body of the response contains Conversation not found
-      And The token metrics should not have changed
+      And The token metrics are not changed
 
 Scenario: Check if LLM responds to sent question with error when attempting to access conversation with incorrect conversation ID format
      When I use "query" to ask question with authorization header
@@ -92,7 +92,7 @@ Scenario: Check if LLM responds for query request with error for missing query
         """
         { "detail": [{"type": "missing", "loc": [ "body", "query" ], "msg": "Field required", "input": {"provider": "{PROVIDER}"}}] }
         """
-      And The token metrics should not have changed
+      And The token metrics are not changed
 
   Scenario: Check if LLM responds for query request for missing model and provider
      When I use "query" to ask question with authorization header