codeceptjs 3.6.0-beta.1.ai-healers → 3.6.1

package/docs/puppeteer.md

@@ -1,316 +0,0 @@
----
-permalink: /puppeteer
-title: Testing with Puppeteer
----
-
-# Testing with Puppeteer
-
-Among all Selenium alternatives the most interesting emerging ones are tools developed around Google Chrome [DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/). And the most prominent one is [Puppeteer](https://github.com/GoogleChrome/puppeteer). It operates over Google Chrome directly without requiring additional tools like ChromeDriver. So tests setup with Puppeteer can be started with npm install only. If you want get faster and simpler to setup tests, Puppeteer would be your choice.
-
-CodeceptJS uses Puppeteer to improve end to end testing experience. No need to learn the syntax of a new tool, all drivers in CodeceptJS share the same API.
-
-Take a look at a sample test:
-
-```js
-I.amOnPage('https://github.com');
-I.click('Sign in', '//html/body/div[1]/header');
-I.see('Sign in to GitHub', 'h1');
-I.fillField('Username or email address', 'something@totest.com');
-I.fillField('Password', '123456');
-I.click('Sign in');
-I.see('Incorrect username or password.', '.flash-error');
-```
-
-It's readable and simple and works using Puppeteer API!
-
-## Setup
-
-To start you need CodeceptJS with Puppeteer packages installed
-
-```bash
-npm install codeceptjs puppeteer --save
-```
-
-Or see [alternative installation options](https://codecept.io/installation/)
-
-> If you already have CodeceptJS project, just install `puppeteer` package and enable a helper it in config.
-
-And a basic project initialized
-
-```sh
-npx codeceptjs init
-```
-
-You will be asked for a Helper to use, you should select Puppeteer and provide url of a website you are testing.
-
-> Puppeteer can also work with Firefox. [Learn how to set it up](/helpers/Puppeteer-firefox)
-
-## Configuring
-
-Make sure `Puppeteer` helper is enabled in `codecept.conf.js` config:
-
-```js
-{ // ..
-  helpers: {
-    Puppeteer: {
-      url: "http://localhost",
-      show: true
-    }
-  }
-  // ..
-}
-```
-
-> Turn off the `show` option if you want to run test in headless mode.
-
-Puppeteer uses different strategies to detect if a page is loaded. In configuration use `waitForNavigation` option for that:
-
-By default it is set to `domcontentloaded` which waits for `DOMContentLoaded` event being fired. However, for Single Page Applications it's more useful to set this value to `networkidle0` which waits for all network connections to be finished.
-
-```js
-  helpers: {
-    Puppeteer: {
-      url: "http://localhost",
-      show: true,
-      waitForNavigation: "networkidle0"
-    }
-  }
-```
-
-When a test runs faster than application it is recommended to increase `waitForAction` config value.
-It will wait for a small amount of time (100ms) by default after each user action is taken.
-
-> ▶ More options are listed in [helper reference](https://codecept.io/helpers/Puppeteer/).
-
-## Writing Tests
-
-CodeceptJS test should be created with `gt` command:
-
-```sh
-npx codeceptjs gt
-```
-
-As an example we will use `ToDoMvc` app for testing.
-
-### Actions
-
-Tests consist with a scenario of user's action taken on a page. The most widely used ones are:
-
-* `amOnPage` - to open a webpage (accepts relative or absolute url)
-* `click` - to locate a button or link and click on it
-* `fillField` - to enter a text inside a field
-* `selectOption`, `checkOption` - to interact with a form
-* `wait*` to wait for some parts of page to be fully rendered (important for testing SPA)
-* `grab*` to get values from page sources
-* `see`, `dontSee` - to check for a text on a page
-* `seeElement`, `dontSeeElement` - to check for elements on a page
-
-> ℹ  All actions are listed in [Puppeteer helper reference](https://codecept.io/helpers/Puppeteer/).*
-
-All actions which interact with elements **support CSS and XPath locators**. Actions like `click` or `fillField` by locate elements by their name or value on a page:
-
-```js
-// search for link or button
-I.click('Login');
-// locate field by its label
-I.fillField('Name', 'Miles');
-// we can use input name
-I.fillField('user[email]','miles@davis.com');
-```
-
-You can also specify the exact locator type with strict locators:
-
-```js
-I.click({css: 'button.red'});
-I.fillField({name: 'user[email]'},'miles@davis.com');
-I.seeElement({xpath: '//body/header'});
-```
-
-### Interactive Pause
-
-It's easy to start writing a test if you use [interactive pause](/basics#debug). Just open a web page and pause execution.
-
-```js
-Feature('Sample Test');
-
-Scenario('open my website', ({ I }) => {
-  I.amOnPage('http://todomvc.com/examples/react/');
-  pause();
-});
-```
-
-This is just enough to run a test, open a browser, and think what to do next to write a test case.
-
-When you execute such test with `codeceptjs run` command you may see the browser is started
-
-```
-npx codeceptjs run --steps
-```
-
-After a page is opened a full control of a browser is given to a terminal. Type in different commands such as `click`, `see`, `fillField` to write the test. A successful commands will be saved to `./output/cli-history` file and can be copied into a test.
-
-A complete ToDo-MVC test may look like:
-
-```js
-Feature('ToDo');
-
-Scenario('create todo item', ({ I }) => {
-  I.amOnPage('http://todomvc.com/examples/react/');
-  I.dontSeeElement('.todo-count');
-  I.fillField('What needs to be done?', 'Write a guide');
-  I.pressKey('Enter');
-  I.see('Write a guide', '.todo-list');
-  I.see('1 item left', '.todo-count');
-});
-```
-
-### Grabbers
-
-If you need to get element's value inside a test you can use `grab*` methods. They should be used with `await` operator inside `async` function:
-
-```js
-const assert = require('assert');
-Scenario('get value of current tasks', async ({ I }) => {
-  I.fillField('.todo', 'my first item');
-  I.pressKey('Enter')
-  I.fillField('.todo', 'my second item');
-  I.pressKey('Enter')
-  let numTodos = await I.grabTextFrom('.todo-count strong');
-  assert.equal(2, numTodos);
-});
-```
-
-### Within
-
-In case some actions should be taken inside one element (a container or modal window or iframe) you can use `within` block to narrow the scope.
-Please take a note that you can't use within inside another within in Puppeteer helper:
-
-```js
-await within('.todoapp', () => {
-  I.fillField('.todo', 'my new item');
-  I.pressKey('Enter')
-  I.see('1 item left', '.todo-count');
-  I.click('.todo-list input.toggle');
-});
-I.see('0 items left', '.todo-count');
-```
-
-### Each Element <Badge text="Since 3.3" type="warning"/>
-
-Usually, CodeceptJS performs an action on the first matched element. 
-In case you want to do an action on each element found, use the special function `eachElement` which comes from [eachElement](https://codecept.io/plugins/#eachelement) plugin. 
-
-`eachElement` function matches all elements by locator and performs a callback on each of those element. A callback function receives [ElementHandle instance](https://pptr.dev/#?product=Puppeteer&show=api-class-elementhandle) from Puppeteer API. `eachElement` may perform arbitrary actions on a page, so the first argument should by a description of the actions performed. This description will be used for logging purposes.
-
-Usage example
-
-```js
-await eachElement(
-  'click all checkboxes', 
-  'input.custom-checkbox', 
-  async (el, index) => {
-    await el.click();
-  });
-);
-```
-
-> ℹ Learn more about [eachElement plugin](/plugins/#eachelement)
-
-## Mocking Requests
-
-Web application sends various requests to local services (Rest API, GraphQL) or to 3rd party services (CDNS, Google Analytics, etc).
-When you run tests with Puppeteer you can control those requests by mocking them. For instance, you can speed up your tests by blocking trackers, Google Analytics, and other services you don't control.
-
-Also you can replace real request with a one explicitly defined. This is useful when you want to isolate application testing from a backend. For instance, if you don't want to save data to database, and you know the request which performs save, you can mock the request, so application will treat this as valid response, but no data will be actually saved.
-
-To mock requests enable additional helper [MockRequest](/helpers/MockRequest) (which is based on Polly.js).
-
-```js
-helpers: {
-   Puppeteer: {
-     // regular Puppeteer config here
-   },
-   MockRequest: {}
-}
-```
-
-And install additional packages:
-
-```
-npm i @pollyjs/core @pollyjs/adapter-puppeteer --save-dev
-```
-
-After an installation function `mockRequest` will be added to `I` object. You can use it to explicitly define which requests to block and which response they should return instead:
-
-```js
-// block all Google Analytics calls
-I.mockRequest('/google-analytics/*path', 200);
-// return an empty successful response
-I.mockRequest('GET', '/api/users', 200);
-// block post requests to /api/users and return predefined object
-I.mockRequest('POST', '/api/users', { user: 'davert' });
-// return error request with body
-I.mockRequest('GET', '/api/users/1', 404, { error: 'User not found' });
-```
-
-> See [`mockRequest` API](/helpers/MockRequest#mockrequest)
-
-To see `mockRequest` method in intellisense auto completion don't forget to run `codeceptjs def` command:
-
-```
-npx codeceptjs def
-```
-
-Mocking rules will be kept while a test is running. To stop mocking use `I.stopMocking()` command
-
-
-## Accessing Puppeteer API
-
-To get Puppeteer API inside a test use [`I.usePupepteerTo`](/helpers/Puppeteer/#usepuppeteerto) method with a callback.
-To keep test readable provide a description of a callback inside the first parameter.
-
-```js
-I.usePuppeteerTo('emulate offline mode', async ({ page, browser }) => {
-  await page.setOfflineMode(true);
-});
-```
-
-> Puppeteer commands are asynchronous so a callback function must be async.
-
-A Puppeteer helper is passed as argument for callback, so you can combine Puppeteer API with CodeceptJS API:
-
-```js
-I.usePuppeteerTo('emulate offline mode', async (Puppeteer) => {
-  // access internal objects browser, page, context of helper
-  await Puppeteer.page.setOfflineMode(true);
-  // call a method of helper, await is required here
-  await Puppeteer.click('Reload');
-});
-```
-
-
-## Extending Helper
-
-To create custom `I.*` commands using Puppeteer API you need to create a custom helper.
-
-Start with creating an `MyPuppeteer` helper using `generate:helper` or `gh` command:
-
-```sh
-npx codeceptjs gh
-```
-
-Then inside a Helper you can access `Puppeteer` helper of CodeceptJS.
-Let's say you want to create `I.renderPageToPdf` action. In this case you need to call `pdf` method of `page` object
-
-```js
-// inside a MyPuppeteer helper
-async renderPageToPdf() {
-  const page = this.helpers['Puppeteer'].page;
-  await page.emulateMedia('screen');
-  return page.pdf({path: 'page.pdf'});
-}
-```
-
-The same way you can also access `browser` object to implement more actions or handle events.
-
-> [▶ Learn more about Helpers](https://codecept.io/helpers/)

package/docs/quickstart.md

@@ -1,162 +0,0 @@
----
-permalink: quickstart
-title: Quickstart
-layout: Section
-sidebar: true
----
-
-::: slot sidebar
-
-#### Use WebDriver for classical Selenium setup
-
-<small>
-This gives you access to rich Selenium ecosystem and cross-browser support for majority of browsers and devices.
-</small>
-
-
-<a href="/webdriver" class="button extended" >Start with WebDriver &raquo;</a>
-
-<small> WebDriver support is implemented via [webdriverio](https://webdriver.io) library </small>
-
----
-
-#### Use TestCafe for cross-browser testing without Selenium
-
-<small>
-TestCafe provides cross-browser support without Selenium. TestCafe tests are faster, require no extra tooling and faster than regular Selenium. However, can be less stable.
-</small>
-
-<a href="/testcafe" class="button green extended" >Start with TestCafe &raquo;</a>
-
----
-
-* [Mobile Testing with Appium »](/mobile)
-
-:::
-
-# Quickstart
-
-
-Use [CodeceptJS all-in-one installer](https://github.com/codeceptjs/create-codeceptjs) to get CodeceptJS, a demo project, and Playwright.
-
-```
-npx create-codeceptjs .
-```
-
-If you prefer not to use Playwright see other [installation options](/installation/).
-
-![Installation](/img/codeceptinstall.gif)
-
-> To install codeceptjs into a different folder, like `tests` use `npx create-codeceptjs tests`
-
-After CodeceptJS is installed, try running **demo tests** using this commands:
-
-* `npm run codeceptjs:demo` - executes demo tests in window mode
-* `npm run codeceptjs:demo:headless` - executes demo tests in headless mode
-* `npm run codeceptjs:demo:ui` - open CodeceptJS UI to list and run demo tests. 
-
-[CodeceptJS UI](/ui) application:
-
-![](https://user-images.githubusercontent.com/220264/93860826-4d5fbc80-fcc8-11ea-99dc-af816f3db466.png)
-
----
-
-### Init
-
-To start a new project initialize CodeceptJS to create main config file: `codecept.conf.js`.
-
-```
-npx codeceptjs init
-```
-
-Answer questions, agree on defaults:
-
-
-| Question | Default Answer  | Alternative
-|---|---|---|
-| Do you plan to write tests in TypeScript?  | **n** (No)  | or [learn how to use TypeScript](/typescript)
-| Where are your tests located? | `**./*_test.js` | or any glob pattern like `**.spec.js`
-| What helpers do you want to use? | **Playwright** | Which helper to use for: [web testing](https://codecept.io/basics/#architecture), [mobile testing](https://codecept.io/mobile/), [API testing](https://codecept.io/api/)
-| Where should logs, screenshots, and reports to be stored? | `./output` | path to store artifacts and temporary files 
-| Do you want to enable localization for tests? | **n** English (no localization) | or write [localized tests](https://codecept.io/translation/) in your language
-  
-
-Sample output:
-
-```js
-? Do you plan to write tests in TypeScript? 'No'
-? Where are your tests located? '**./*_test.js'
-? What helpers do you want to use? 'Playwright'
-? Where should logs, screenshots, and reports to be stored? '**./output**'
-? Do you want to enable localization for tests? 'English (no localization)'
-```
-
-For Playwright helper provide a website to be tested and browser to be used:
-
-| Question | Default Answer  | Alternative
-|---|---|---|
-| Base url of site to be tested | http://localhost | Base URL of website you plan to test. Use http://github.com or [sample checkout page](https://getbootstrap.com/docs/5.2/examples/checkout/) if you just want to play around
-| Show browser window | **y** Yes | or run browser in **headless mode** 
-| Browser in which testing will be performed | **chromium** | or run tests in firefox, webkit (which is opensource version of Safari) or launch electron app
-
-```js
-? [Playwright] Base url of site to be tested 'http://mysite.com'
-? [Playwright] Show browser window 'Yes'
-? [Playwright] Browser in which testing will be performed. Possible options: chromium, firefox, webkit or electron 'chromium'
-
-```
-
-Create first feature and test when asked
-
-Open a newly created file in your favorite JavaScript editor. 
-The file should look like this:
-
-```js
-Feature('My First Test');
-
-Scenario('test something', ({ I }) => {
-
-});
-```
-Write a simple test scenario:
-
-```js
-Feature('My First Test');
-
-Scenario('test something', ({ I }) => {
-  I.amOnPage('https://github.com');
-  I.see('GitHub');
-});
-```
-
-Run a test:
-
-```
-npx codeceptjs run
-```
-
-The output should be similar to this:
-
-```bash
-My First Test --
-  test something
-     I am on page "https://github.com"
-     I see "GitHub"
- ✓ OK
-```
-
-To quickly execute tests use following npm scripts:
-
-After CodeceptJS is installed, try running **demo tests** using this commands:
-
-* `npm run codeceptjs` - executes tests in window mode
-* `npm run codeceptjs:headless` - executes tests in headless mode
-* `npm run codeceptjs:ui` - open CodeceptJS UI to list and run tests. 
-
-More commands available in [CodeceptJS CLI runner](https://codecept.io/commands/).
-
-
-> [▶ Next: CodeceptJS Basics](/basics/)
-
-> [▶ Next: CodeceptJS with Playwright](/playwright/)
-

package/docs/react.md

@@ -1,70 +0,0 @@
----
-permalink: /react
-title: Testing React Applications
----
-
-# Testing React Applications
-
-React applications require some additional love for end to end testing.
-At first, it is very hard to test an application which was never designed to be tested!
-This happens to many React application. While building components developers often forget to keep the element's semantic.
-
-Generated HTML code may often look like this:
-
-```js
-<div class="jss607 jss869 jss618 jss871 jss874 jss876" tabindex="0" role="tab" aria-selected="true" style="pointer-events: auto;">
-  <span class="jss877">
-    <span class="jss878">
-      <span class="jss879">Click Me!</span>
-    </span>
-  </span>
-<span class="jss610"></span></div>
-```
-
-It's quite common that clickable elements are not actual `a` or `button` elements. This way `I.click('Click Me!');` won't work, as well as `fillField('name', 'value)`. Finding a correct locator for such cases turns to be almost impossible.
-
-In this case test engineers have two options:
-
-1. Update JSX files to change output HTML and rebuild the application
-1. Test the application how it is.
-
-We recommend for long-running projects to go with the first option. The better you write your initial HTML the cleaner and less fragile will be your tests. Replace divs with correct HTML elements, add `data-` attributes, add labels, and names to input fields to make all CodeceptJS magic like clicking link by a text to work.
-
-However, if you can't update the code you can go to the second option. In this case, you should bind your locators to visible text on page and available semantic attribues. For instance, instead of using generated locator as this one:
-
-```
-//*[@id="document"]/div[2]/div/div[2]/div
-```
-
-use [Locator Builder](/locators#locator-builder) to make clean semantic locator:
-
-```js
-locate('[role=tab]').withText('Click Me!');
-```
-
-This way you can build very flexible and stable locators even on application never designed for testing.
-
-## Locators
-
-For React apps a special `react` locator is available. It allows to select an element by its component name, props and state.
-
-```js
-{ react: 'MyComponent' }
-{ react: 'Button', props: { title: 'Click Me' }}
-{ react: 'Button', state: { some: 'state' }}
-{ react: 'Input', state: 'valid'}
-```
-
-In WebDriver, Puppeteer, and Playwright you can use React locators in any method where locator is required:
-
-```js
-I.click({ react: 'Tab', props: { title: 'Click Me!' }});
-I.seeElement({ react: 't', props: { title: 'Clicked' }});
-```
-
-To find React element names and props in a tree use [React DevTools](https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi) extension.
-
-> Turn off minification for application builds otherwise component names will be uglified as well
-
-- With WebDriver and Puppeteer, React locators work via [resq](https://github.com/baruchvlz/resq) library, which handles React 16 and above.
-- With Playwright, React locators work via [Playwright React Locator](https://playwright.dev/docs/other-locators#react-locator).