@cuppet/core

Core testing framework components for Cuppet - a BDD framework based on Cucumber and Puppeteer.

Installation

``bash
yarn install @cuppet/core
`

Usage

$3

`bash
yarn install
`

$3

`bash
yarn test
`

Available Components

$3

- elementInteraction - Element interaction utilities
- dataStorage - Data storage and management
- mainFunctions - Main testing functions
- helperFunctions - Helper utilities
- apiFunctions - API testing functions
- appiumTesting - Appium mobile testing
- accessibilityTesting - Accessibility testing with Pa11y
- lighthouse - Performance testing with Lighthouse
- visualRegression - Visual regression testing with BackstopJS

$3

- BrowserManager - Puppeteer browser management
- AppiumManager - Appium mobile testing management

$3

- stepDefinitions - Pre-built Cucumber step definitions for common testing scenarios

Using Step Definitions in Other Projects

The cuppet-core package includes pre-built step definitions that you can use in your main project. Here are several ways to integrate them:

$3

Make sure your Cucumber configuration includes the step definition paths:

`javascript
// cucumber.js
module.exports = {
default: {
requireModule: ['@cuppet/core'],
require: [
'node_modules/@cuppet/core/features/app/stepDefinitions/*.js',
'features/step-definitions/*/.js', // Your project's step definitions
],
},
};
`

$3

`javascript
// Import step definitions directly
const stepDefinitions = require('@cuppet/core/stepDefinitions');

// Or import specific step definition modules
const generalSteps = require('@cuppet/core/features/app/stepDefinitions/generalSteps');
const apiSteps = require('@cuppet/core/features/app/stepDefinitions/apiSteps');
const { Then } = require('@cucumber/cucumber');

Then('the response should be an {string}', async function (type) {
console.log('Add your new custom logic', type);
});
`

$3

`javascript
// In your project's step definition file
const { Given, When, Then } = require('@cucumber/cucumber');
const generalSteps = require('@cuppet/core/features/app/stepDefinitions/generalSteps');

// Extend the base step definitions with your custom logic
Given('I am logged in as {string}', async function (userName) {
// Your custom login logic
await this.page.goto('https://your-app.com/login');
await this.page.fill('[data-testid="username"]', userName);
await this.page.fill('[data-testid="password"]', 'password');
await this.page.click('[data-testid="login-button"]');

// Then use a base step definition
await generalSteps.['I follow {string}'].call(this,userName);
});
`

$3

- accessibilitySteps - Accessibility testing steps
- apiSteps - API testing and validation steps
- appiumSteps - Mobile testing with Appium
- generalSteps - Common navigation and interaction steps
- helperSteps - Utility and helper steps
- iframeSteps - Iframe handling steps
- ifVisibleSteps - Conditional visibility steps
- lighthouseSteps - Performance testing steps
- pageElements - Page element testing
- pageElementsConfig - Page element testing with values from config
- pageElementsJson - Page element testing with values from locally stored JSON file
- visualRegressionSteps - Visual regression testing steps

Project-Specific Components

The following components should be created in your project as they are specific to your application:

- commonComponents/ - Common form fields and page paths for your application
- multilingualStrings/ - Multilingual string support for your application

Comprehensive configurations and usage guide

For a detailed configuration and step definitions guide, see GUIDE.MD.

Peer Dependencies

This package requires the following peer dependencies:

- @cucumber/cucumber ^12.0.0
- config ^4.1.0

Make sure to install these in your project:

`bash
yarn install @cucumber/cucumber config
``

Contributing

We welcome contributions! Please see our Contributing Guide for details on how to submit pull requests and our development workflow.

For detailed development setup and publishing information, check out our Development Guide.

License

ISC