Added docs for playwright

packages/noco-docs/content/en/engineering/playwright.md

@@ -0,0 +1,224 @@
+---
+title: "Playwright E2E testing"
+description: "Overview to playwright based e2e tests"
+position: 3260
+category: "Engineering"
+menuTitle: "Playwright E2E testing"
+---
+
+## How to run tests
+
+All the tests reside in `tests/playwright` folder.
+
+Make sure to install the dependencies(in the playwright folder):
+
+```bash
+npm install
+npx playwright install chromium --with-deps
+```
+
+### Run Test Server
+
+Start the backend test server (in `packages/nocodb` folder):
+
+```bash
+npm run watch:run:playwright
+```
+
+Start the frontend test server (in `packages/nc-gui` folder):
+
+```bash
+NUXT_PAGE_TRANSITION_DISABLE=true npm run dev
+```
+
+### Running all tests
+
+For selecting db type, rename `.env.example` to `.env` and set `E2E_DEV_DB_TYPE` to  `sqlite`(default), `mysql` or `pg`.
+
+headless mode(without opening browser):
+
+```bash
+npm run test
+```
+
+with browser:
+
+```bash
+npm run test:debug
+```
+
+</br>
+</br>
+
+For setting up mysql(sakila):
+
+```bash
+docker-compose -f ./tests/playwright/scripts/docker-compose-mysql-playwright.yml  up -d
+```
+
+For setting up postgres(sakila):
+
+```bash
+docker-compose -f ./tests/playwright/scripts/docker-compose-playwright-pg.yml 
+```
+
+### Running individual tests
+
+Add `.only` to the test you want to run:
+
+```js
+test.only('should login', async ({ page }) => {
+  // ...
+})
+```
+
+```bash
+npm run test
+```
+
+## Concepts
+
+### Independent tests
+
+- All tests are independent of each other.
+- Each test starts with a fresh project with a fresh sakila database(option to not use sakila db is also there).
+- Each test creates a new user(email as `user@nocodb.com`) and logs in with that user to the dashboard.
+
+Caveats:
+
+- Some stuffs are shared i.e, users, plugins etc. So be catious while writing tests touching that. A fix for this is in the works.
+- In test, we prefix email and project with the test id, which will be deleted after the test is done.
+
+### What to test
+
+- UI verification. This includes verifying the state of the UI element, i.e if the element is visible, if the element has a particular text etc.
+- Test should verify all user flow. A test has a default timeout of 60 seconds. If a test is taking more than 60 seconds, it is a sign that the test should be broken down into smaller tests.
+- Test should also verify all the side effects the feature(i.e. On adding a new column type, should verify column deletion as well) will have, and also error cases.
+- Test name should be descriptive. It should be easy to understand what the test is doing by just reading the test name.
+
+### Playwright
+
+- Playwright is a nodejs library for automating chromium, firefox and webkit.
+- For each test, a new browser context is created. This means that each test runs in a new incognito window.
+- For assertion always use `expect` from `@playwright/test` library. This library provides a lot of useful assertions, which also has retry logic built in.
+
+## Page Objects
+
+- Page objects are used to abstract over the components/page. This makes the tests more readable and maintainable.
+- All page objects are in `tests/playwright/pages` folder.
+- All the test related code should be in page objects.
+- Methods should be as thin as possible and its better to have multiple methods than one big method, which improves reusability.
+
+The methods of a page object can be classified into 2 categories:
+
+- Actions: Performs an UI actions like click, type, select etc. Is also responsible for waiting for the element to be ready and the action to be performed. This included waiting for api calls to complete.
+- Assertions: Asserts the state of the UI element, i.e if the element is visible, if the element has a particular text etc. Use `expect` from `@playwright/test` and if not use `expect.poll` to wait for the assertion to pass.
+
+## Writing a test
+
+Let's write a test for testing filter functionality.
+
+For simplicity, we will have `DashboardPage` implemented, which will have all the methods related to dashboard page and also its child components like Grid, etc.
+
+### Create a test suite
+
+Create a new file `filter.spec.ts` in `tests/playwright/tests` folder and use `setup` method to create a new project and user.
+
+```js
+import { test, expect } from '@playwright/test';
+import setup, { NcContext } from '../setup';
+
+test.describe('Filter', () => {
+  let context: NcContext;
+
+  test.beforeEach(async ({ page }) => {
+    context = await setup({ page });
+  })
+
+  test('should filter', async ({ page }) => {
+    // ...
+  });
+});
+```
+
+### Create a page object
+
+Since filter is UI wise scoped to a `Toolbar` , we will add filter page object to `ToolbarPage` page object.
+
+```js
+export class ToolbarPage extends BasePage {
+  readonly parent: GridPage | GalleryPage | FormPage | KanbanPage;
+  readonly filter: ToolbarFilterPage;
+
+  constructor(parent: GridPage | GalleryPage | FormPage | KanbanPage) {
+    super(parent.rootPage);
+    this.parent = parent;
+    this.filter = new ToolbarFilterPage(this);
+  }
+}
+```
+
+We will create `ToolbarFilterPage` page object, which will have all the methods related to filter.
+
+```js
+export class ToolbarFilterPage extends BasePage {
+  readonly toolbar: ToolbarPage;
+
+  constructor(toolbar: ToolbarPage) {
+    super(toolbar.rootPage);
+    this.toolbar = toolbar;
+  }
+}
+```
+
+Here `BasePage` is an abstract class, which used to enforce structure for all page objects. Thus all page object *should* inherit `BasePage`.
+
+- Helper methods like `waitForResponse` and `getClipboardText` (this can be access on any page object, with `this.waitForResponse`)
+- Provides structure for page objects, enforces all Page objects to have `rootPage` property, which is the page object created in the test setup.
+- Enforces all pages to have a `get` method which will return the locator of the main container of that page, hence we can have focused dom selection, i.e.
+
+```js
+// This will only select the button inside the container of the concerned page
+await this.get().querySelector('button').count();
+```
+
+### Writing an action method
+
+This a method which will reset/clear all the filters. Since this is an action method, it will also wait for the `delete` filter api to return. Ignoring this api call will cause flakiness in the test, down the line.
+
+```js
+async resetFilter() {
+  await this.waitForResponse({
+    uiAction: this.get().locator('.nc-filter-item-remove-btn').click(),
+    httpMethodsToMatch: ['DELETE'],
+    requestUrlPathToMatch: '/api/v1/db/meta/filters/',
+  });
+}
+```
+
+### Writing an assertion/verification method
+
+Here we use `expect` from `@playwright/test` library, which has retry logic built in.
+
+```js
+import { expect } from '@playwright/test';
+
+async verifyFilter({ title }: { title: string }) {
+  await expect(
+    this.get().locator(`[data-testid="nc-fields-menu-${title}"]`).locator('input[type="checkbox"]')
+  ).toBeChecked();
+}
+```
+
+## Tips to avoid flakiness
+
+- If an ui action, causes an api call or the UI state change, then wait for that api call to complete or the UI state to change.
+- What to wait out can be situation specific, but in general, is best to wait for the final state to be reached, i.e. in the case of creating filter, while it seems like waiting for the filter api to complete is enough, but after its return the table rows are reloaded and the UI state changes, so its better to wait for the table rows to be reloaded.
+
+
+## Accessing playwright report in the CI
+
+- Open `Summary` tab in the CI workflow in github actions.
+- Scroll down to `Artifacts` section.
+- Access reports which suffixed with the db type and shard number(corresponding to the CI workerflow name). i.e `playwright-report-mysql-2` is for `playwright-mysql-2` workflow.
+- Download it and run `npm install -D @playwright/test && npx playwright show-report ./` inside the downloaded folder.

packages/noco-docs/content/en/engineering/testing.md → packages/noco-docs/content/en/engineering/unit-testing.md

@@ -1,9 +1,9 @@
 ---
-title: "Writing Tests"
-description: "Overview to testing"
+title: "Writing Unit Tests"
+description: "Overview to unit testing"
 position: 3250
 category: "Engineering"
-menuTitle: "Writing Tests"
+menuTitle: "Unit Testing"
 ---
 
 ## Unit Tests
@@ -189,158 +189,3 @@ function tableTest() {
   });
 }
 ```
-
-## Cypress Tests
-
-### End-to-end (E2E) Tests
-Cypress tests are divided into 4 suites
-- SQLite tests
-- Postgres tests
-- MySQL tests
-- Quick import tests
-
-First 3 suites, each have 4 test category
-- Table operations (create, delete, rename, add column, delete column, rename column)
-- Views (Grid, Gallery, Form)
-- Roles (user profiles, access control & preview)
-- Miscellaneous (Import, i18n, etc)
-
-### SQLite Tests (XCDB Project)
-
-```shell
-# install dependencies(cypress)
-npm install
-# start MySQL database using docker compose
-docker-compose -f ./scripts/cypress/docker-compose-cypress.yml up
-
-# Run backend api using following command
-npm run start:xcdb-api:cache
-# Run frontend web UI using following command
-npm run start:web
-
-# wait until both 3000 and 8080 ports are available
-# or run following command to run it with GUI
-npm run cypress:open
-
-# run one of 4 test scripts
-# - Table operations : xcdb-restTableOps.js
-# - Views : xcdb-restViews.js
-# - Roles & access control : xcdb-restRoles.js
-# - Miscellaneous : xcdb-restMisc.js
-```
-
-### MySQL Tests (External DB Project)
-
-```shell
-# install dependencies(cypress)
-npm install
-# start MySQL database using docker compose
-docker-compose -f ./scripts/cypress/docker-compose-cypress.yml up
-
-# Run backend api using following command
-npm run start:api:cache
-# Run frontend web UI using following command
-npm run start:web
-
-# wait until both 3000 and 8080 ports are available
-# or run following command to run it with GUI
-npm run cypress:open
-
-# run one of 4 test scripts
-# - Table operations : restTableOps.js
-# - Views : restViews.js
-# - Roles & access control : restRoles.js
-# - Miscellaneous : restMisc.js
-```
-
-### Postgres Tests (External DB Project)
-
-```shell
-# install dependencies(cypress)
-npm install
-# start Postgres database using docker compose
-docker-compose -f ./scripts/cypress/docker-compose-pg.yml up -d
-
-# Run backend api using following command
-npm run start:api:cache
-# Run frontend web UI using following command
-npm run start:web
-
-# wait until both 3000 and 8080 ports are available
-# or run following command to run it with GUI
-npm run cypress:open
-
-# run one of 4 test scripts
-# - Table operations : pg-restTableOps.js
-# - Views : pg-restViews.js
-# - Roles & access control : pg-restRoles.js
-# - Miscellaneous : pg-restMisc.js
-```
-
-### Quick Import Tests (SQLite Project)
-
-```shell
-# install dependencies(cypress)
-npm install
-# start MySQL database using docker compose
-docker-compose -f ./scripts/cypress/docker-compose-cypress.yml up
-
-# copy existing xcdb (v0.91.7) database to ./packages/nocodb/
-cp ./scripts/cypress/fixtures/quickTest/noco_0_91_7.db ./packages/nocodb/noco.db
-
-# Run backend api using following command
-npm run start:api:cache
-# Run frontend web UI using following command
-npm run start:web
-
-# wait until both 3000 and 8080 ports are available
-# or run following command to run it with GUI
-npm run cypress:open
-
-# run test script
-# - quickTest.js
-```
-
-### Quick import tests (Postgres)
-
-```shell
-# install dependencies(cypress)
-npm install
-# start PG database using docker compose
-docker-compose -f ./scripts/cypress/docker-compose-pg.yml up -d
-
-# copy existing xcdb (v0.91.7) database to ./packages/nocodb/
-cp ./scripts/cypress/fixtures/quickTest/noco_0_91_7.db ./packages/nocodb/noco.db
-
-# Run backend api using following command
-npm run start:api:cache
-# Run frontend web UI using following command
-npm run start:web
-
-# wait until both 3000 and 8080 ports are available
-# or run following command to run it with GUI
-npm run cypress:open
-
-# run test script
-# - quickTest.js
-```
-
-## Accessing CI-CD CY Screenshots
-
-1. On Jobs link, click on `Summary`
-
-
-![Screenshot 2022-10-31 at 9 25 23 PM](https://user-images.githubusercontent.com/86527202/199052696-af0bf066-d82f-487a-b487-602f55594fd7.png)
-
-
-2. Click on `Artifacts`
-
-
-![Screenshot 2022-10-31 at 9 26 01 PM](https://user-images.githubusercontent.com/86527202/199052712-04508921-32b1-4926-8291-396c804f7c3b.png)
-
-
-3. Download logs for desired suite
-
-
-![Screenshot 2022-10-31 at 9 26 34 PM](https://user-images.githubusercontent.com/86527202/199052727-9aebbdd1-749e-4bda-ab00-3cdd0e3f48fe.png)
-