@maxio-com/self-service 1.4.0 → 1.4.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -110,3 +110,37 @@ The end-to-end tests codebase could contain `tags` which refers to specific AIO
110
110
 
111
111
  During manual pipeline execution - the `test_cycle_id` argument could be used to execute only tests cases included in
112
112
  AIO Test Cycle and automatically update execution results.
113
+
114
+ ### How to perform End to End Testing using Playwright locally
115
+
116
+ #### 1. Build RUC package using command:
117
+ ```sh
118
+ pnpm build:browser
119
+ ```
120
+ As a result ``maxio-components.umd.js`` will be created inside ```dist``` folder
121
+
122
+ #### 2. Copy assets into ``e2e_pages`` folder using command:
123
+ ```sh
124
+ pnpm copy:e2e-assets
125
+ ```
126
+ Note: You can use ``pnpm clean:e2e-assets`` to clean old assets first if needed
127
+
128
+ #### 3. Serve pages and assets so playwright can load it properly on specified port:
129
+ ```sh
130
+ pnpm serve:e2e-assets
131
+ ```
132
+
133
+ #### 4. Provide required env variables (you can refer to .env.example)
134
+
135
+ #### 5. Run playwright tests:
136
+ ```sh
137
+ npx playwright test
138
+ ```
139
+
140
+ #### Additional information:
141
+
142
+ - ``playwright.config.ts``: Is playwright configuration file. Anything related to browser, hosts, timeouts, and parallelism can be configured there.
143
+
144
+ - ``--headed`` flag added to ``npx playwright test`` allows to open browser during tests
145
+
146
+ - ``page.pause()`` allows to pause the test execution and do some debugging