k6-cucumber-steps/dist/generators/samples/sample-features.generator.js

Generate k6 test scripts from Cucumber feature files

"use strict";
var __importDefault = (this && this.__importDefault) || function (mod) {
    return (mod && mod.__esModule) ? mod : { "default": mod };
};
Object.defineProperty(exports, "__esModule", { value: true });
exports.SampleFeaturesGenerator = void 0;
// src/generators/samples/sample-features.generator.ts
const fs_1 = __importDefault(require("fs"));
const path_1 = __importDefault(require("path"));
class SampleFeaturesGenerator {
    generate(outputPath) {
        this.generateSampleFeature(outputPath);
        this.generateBrowserSampleFeature(outputPath);
        this.generateAuthSampleFeature(outputPath);
    }
    generateSampleFeature(outputPath) {
        const sampleFeature = `@smoke @vus:10 @duration:1m
Feature: Comprehensive API Testing with Environment Variables

  Background:
    Given the k6 base URL is "{{API_BASE_URL}}"

  @group:user-api @threshold:http_req_duration=p(95)<1000
  Scenario: Get user and validate response
    When I k6 make a GET request to "/users/1"
    Then the k6 response status should be "200"
    And the k6 response should contain "name"
    And the k6 response property "email" should not be empty

  @group:property-validation
  Scenario: Validate response properties and types
    When I k6 make a GET request to "/users/1"
    Then the k6 response status should be "200"
    And the k6 response property "id" should be "1"
    And the k6 response property "name" should contain "Leanne"
    And the k6 response property "company" should have property "name"
    And the k6 response time should be less than "500" milliseconds

  @group:post-api
  Scenario: Create a post with environment variables
    Given I k6 have the following post data:
      """
      {
        "title": "{{POST_TITLE}}",
        "body": "Testing with environment variables",
        "userId": 1
      }
      """
    When I k6 make a POST request to "/posts"
    Then the k6 response status should be "201"
    And the k6 response property "title" should be "{{POST_TITLE}}"
    And I k6 store response "data" as "createdPost"
    And I k6 print alias "createdPost"

  @group:alias-validation
  Scenario: Validate using stored aliases
    Given I k6 have the following post data:
      """
      {
        "title": "Alias Test",
        "body": "Testing alias comparison",
        "userId": 1
      }
      """
    When I k6 make a POST request to "/posts"
    Then the k6 response status should be "201"
    And I k6 store response "data.id" as "postId"
    And the k6 alias "postId" should not be empty
    And I k6 print all aliases

  @group:load-test @stages:0s-0,20s-10,30s-10,10s-0
  Scenario Outline: Validate multiple user endpoints
    When I k6 make a GET request to "/users/<userId>"
    Then the k6 response status should be <expectedStatus>
    And the k6 response time should be less than "1" seconds

    Examples:
      | userId | expectedStatus |
      | 1      | "200"          |
      | 5      | "200"          |
      | 999    | "404"          |
`;
        fs_1.default.writeFileSync(path_1.default.join(outputPath, "features", "sample.feature"), sampleFeature);
    }
    generateBrowserSampleFeature(outputPath) {
        const content = `@iterations:1 @browser
Feature: Comprehensive UI Automation on DemoQA

  Background:
    Given the k6 base URL is "https://demoqa.com"

  Scenario: Fill and submit the practice form successfully
    When I k6 navigate to the "/automation-practice-form" page
    And I k6 fill the field "#firstName" with "Paschal"
    And I k6 fill the field "#lastName" with "Enyimiri"
    And I k6 fill the field "#userEmail" with "paschal.cheps@example.com"
    And I k6 get element by selector "label[for='gender-radio-1']"
    And I k6 click
    And I k6 click on exact text "Male"
    And I k6 fill the field "#userNumber" with "0801234567"
    And I k6 wait "1" seconds
    And I k6 click on exact text "Music"
    And I k6 click on the element "#state"
    And I k6 click on exact text "NCR"
    And I k6 fill the field "#currentAddress" with "this is a load test on the ui"
    And I k6 wait "1" seconds
    And I k6 click on the element "#city"
    And I k6 click on exact text "Delhi"
    And I k6 click on the element "#submit"
    Then I k6 should see the text "Thanks for submitting the form"

  Scenario: Multiple locator strategies
    When I k6 navigate to the "/automation-practice-form" page
    # By ID
    And I k6 find element by Id "firstName"
    # By placeholder
    And I k6 find input element by placeholder text "First Name"
    # By label
    And I k6 find element by label "First Name"
    # By role
    And I k6 find element by role "textbox" "First Name"
    Then I k6 should see the text "Student Registration Form"

  Scenario: Wait and validate dynamic content
    When I k6 navigate to the "/automation-practice-form" page
    And I k6 wait "2" seconds
    And I k6 should see the element "#firstName"
    And I k6 should see the text "Practice Form"
    And the k6 page title should be "DEMOQA"
    And the k6 current URL should contain "automation-practice-form"

  Scenario: Interact with repeated elements
    When I k6 navigate to the "/elements" page
    And I k6 fill the field "#input-field" with "First" "1"
    And I k6 fill the field "#input-field" with "Second" "2"
    And I k6 click on the element "button[type='submit']" "2"
    And I k6 click on the element "button"
`;
        fs_1.default.writeFileSync(path_1.default.join(outputPath, "features", "browserSample.feature"), content);
    }
    generateAuthSampleFeature(outputPath) {
        const content = `@vus:2
Feature: Authentication Examples with Environment Variables

  Background:
    Given the k6 base URL is "{{AUTH_BASE_URL}}"

  Scenario: Authenticate via Standard Login and store token
    When I k6 authenticate with the following url and request body as "standard_user":
      | endpoint               | userName            | password            |
      | /Account/v1/Authorized | {{TEST_USER_USERNAME}} | {{TEST_USER_PASSWORD}} |
    Then the k6 response status should be "200"
    And the k6 response property "accessToken" should not be empty
    And I k6 store "accessToken" in "data/standard_user.json"
    And I k6 store response "accessToken" as "authToken"
    And the k6 alias "authToken" should not be empty

  Scenario: Reuse stored token for authenticated request
    Given I k6 am authenticated as a "standard_user"
    When I k6 make a GET request to "/Account/v1/User/{{TEST_USER_USERNAME}}"
    Then the k6 response status should be "200"
    And the k6 response property "userName" should be "{{TEST_USER_USERNAME}}"

  Scenario: Authenticate via Client Credentials (OAuth2)
    When I k6 authenticate with the following url and request body as "service_account" with "form":
      | endpoint     | client_id         | client_secret     | grant_type         |
      | /oauth/token | {{CLIENT_ID}} | {{CLIENT_SECRET}} | client_credentials |
    Then the k6 response status should be "200"
    And the k6 response property "access_token" should not be empty
    And I k6 store "access_token" in "data/service_account.json"
    And I k6 print alias "service_account"

  Scenario: Validate boolean response properties
    When I k6 authenticate with the following url and request body as "test_user":
      | endpoint               | userName            | password            |
      | /Account/v1/Authorized | {{TEST_USER_USERNAME}} | {{TEST_USER_PASSWORD}} |
    Then the k6 response property "isActive" should be true
    And the k6 response property "isLocked" should be false

  Scenario: Clear auth and verify
    Given I k6 clear auth token
    When I k6 make a GET request to "/Account/v1/User/{{TEST_USER_USERNAME}}"
    Then the k6 response status should be "401"

  Scenario: Compare response with stored aliases
    When I k6 authenticate with the following url and request body as "user1":
      | endpoint               | userName            | password            |
      | /Account/v1/Authorized | {{TEST_USER_USERNAME}} | {{TEST_USER_PASSWORD}} |
    And I k6 store response "userName" as "expectedUsername"
    Then the k6 response property "userName" should be alias "expectedUsername"
`;
        fs_1.default.writeFileSync(path_1.default.join(outputPath, "features", "authSample.feature"), content);
    }
}
exports.SampleFeaturesGenerator = SampleFeaturesGenerator;
//# sourceMappingURL=sample-features.generator.js.map