codeceptjs 4.0.0-rc.18 → 4.0.0-rc.19

package/docs/puppeteer.md

@@ -0,0 +1,314 @@
+---
+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/puppeteer/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
+import assert from '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 Network Requests <Badge text="Since 3.5.16" type="warning"/>
+
+Network requests & responses can be mocked and modified. Use `mockRoute` which strictly follows [Puppeteer's `setRequestInterception` API](https://pptr.dev/next/api/puppeteer.page.setrequestinterception).
+
+```js
+I.mockRoute('https://reqres.in/api/comments/1', request => {
+  request.respond({
+    status: 200,
+    headers: { 'Access-Control-Allow-Origin': '*' },
+    contentType: 'application/json',
+    body: '{"name": "this was mocked" }',
+  });
+})
+
+I.mockRoute('**/*.{png,jpg,jpeg}', route => route.abort());
+
+// To disable mocking for a route call `stopMockingRoute`
+// for previously mocked URL
+I.stopMockingRoute('**/*.{png,jpg,jpeg}'
+```
+
+To master request intercepting [use `HTTPRequest` object](https://pptr.dev/next/api/puppeteer.httprequest) object passed into mock request handler.
+
+## 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')
+})
+```
+
+## Capturing Code Coverage
+
+Code coverage can be captured, by enabling the `coverage` plugin in `codecept.config.js`.
+
+```js
+{
+  plugins: {
+    coverage: {
+      enabled: true
+    }
+  }
+}
+```
+
+Once all the tests are completed, `codecept` will create and store coverage in `output/coverage` folder, as shown below.
+
+![](<(https://github.com/codeceptjs/CodeceptJS/assets/7845001/3b8b81a3-7c85-470c-992d-ecdc7d5b4a1e)>)
+
+Open `index.html` in your browser to view the full interactive coverage report.
+
+![](https://github.com/codeceptjs/CodeceptJS/assets/7845001/f45607ed-dbe8-4ed4-9b21-01ce25288d22)
+
+![](https://github.com/codeceptjs/CodeceptJS/assets/7845001/c821ce45-6590-4ace-b7ae-2cafb3a4e532)
+
+## 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

@@ -0,0 +1,120 @@
+---
+permalink: quickstart
+title: Quickstart
+layout: Section
+sidebar: true
+---
+
+# Quickstart
+
+Install CodeceptJS into your project:
+
+```
+npm install codeceptjs playwright --save-dev
+```
+
+Then install the browser binaries:
+
+```
+npx playwright install --with-deps
+```
+
+The `--with-deps` flag also installs required system dependencies for the browsers.
+
+> Prefer WebDriver or Appium? See [installation options](/installation/) for all supported helpers.
+
+---
+
+### Init
+
+Initialize CodeceptJS to set up the config file and test directory:
+
+```
+npx codeceptjs init
+```
+
+This command walks you through a short setup wizard and creates `codecept.conf.js`, a sample test file, and any required browser binaries.
+
+Answer the questions, accepting defaults to get started quickly:
+
+| 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** | See options 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 be stored? | `./output` | path to store artifacts and temporary files
+
+For Playwright, you'll also be asked about the site and browser:
+
+| Question | Default Answer  | Alternative
+|---|---|---|
+| Base url of site to be tested | http://localhost | URL of the site you plan to test
+| Show browser window | **y** Yes | or run in **headless mode**
+| Browser | **chromium** | or `firefox`, `webkit` (open-source Safari), or `electron`
+
+Sample output:
+
+```
+? 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 be stored? ./output
+? [Playwright] Base url of site to be tested http://localhost
+? [Playwright] Show browser window Yes
+? [Playwright] Browser in which testing will be performed chromium
+```
+
+When asked, create your first feature and test file.
+
+---
+
+### Write Your First Test
+
+Open the generated test file. It will look like this:
+
+```js
+Feature('My First Test');
+
+Scenario('test something', ({ I }) => {
+
+});
+```
+
+Add a simple scenario:
+
+```js
+Feature('My First Test');
+
+Scenario('test something', ({ I }) => {
+  I.amOnPage('https://github.com');
+  I.see('GitHub');
+});
+```
+
+---
+
+### Run Tests
+
+```
+npx codeceptjs run
+```
+
+Expected output:
+
+```bash
+My First Test --
+  test something
+     I am on page "https://github.com"
+     I see "GitHub"
+ ✓ OK
+```
+
+Run in headless mode:
+
+```
+npx codeceptjs run --headless
+```
+
+See all available commands in the [CLI reference](https://codecept.io/commands/).
+
+> [▶ Next: CodeceptJS Basics](/basics/)

package/docs/react.md

@@ -0,0 +1,70 @@
+---
+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).