How klassijs/klassijs-example-project works
Project type and purpose
• This is an automated test‐automation framework written in Node.js.
• It uses WebdriverIO with Cucumber (BDD) to execute end-to-end web tests.
• It is structured as a template/test suite, integrating with local browsers (via Selenium) or cloud browsers (via LambdaTest), and CI (CircleCI).
File structure
• Top-level config:
• .circleci/config.yml.template – CI pipeline
• .dataConfigrc.js, .envConfigrc.js – data/env configuration
• cucumber.js – Cucumber runner config
• package.json, pnpm-lock.yaml – Node.js dependencies & scripts
• Core test directories:
• features/ – Cucumber .feature files (Scenarios)
• step_definitions/ – glue code mapping Gherkin steps to JS functions
• page-objects/ – Page Object Model classes encapsulating UI selectors & actions
• shared-objects/ – reusable test data & utility objects
• Helpers: The README lists many helper methods (helpers.*) exposed to step definitions.
• lambdatest/ – browser configurations for remote execution
• settings/ – common/shared settings for environments or test runs
Architecture insights from README
• BDD flow (@tags, feature files → step_defs → helpers + page objects → browser)
• Pluggable options (CLI switches for browser, tags, feature paths, reports, remote service)
• Reporting: local HTML reports, email notifications, visual comparisons, JSON→Excel
• CI/CD: CircleCI integration via config template, Husky/Git hooks for commit conventions