E2E: Playwright e2e tests

e2e-playwright/config/cucumber.js

@@ -1,7 +1,7 @@
 /* eslint-disable */
 module.exports = {
     default: {
-        timeout: 30000,
+        timeout: 60000,
         tags: process.env.npm_config_TAGS || "",
         formatOptions: {
             snippetInterface: "async-await"

e2e-playwright/package.json

@@ -7,6 +7,7 @@
     "pretest": "npx ts-node src/helper/report/init.ts",
     "test": "cross-env ENV=prod FORCE_COLOR=0 cucumber-js --config=config/cucumber.js",
     "test:stage": "cross-env ENV=stage FORCE_COLOR=0 cucumber-js --config=config/cucumber.js",
+    "test:sp": "cross-env ENV=stage FORCE_COLOR=0 cucumber-js --config=config/cucumber.js --tags @sp",
     "posttest": "npx ts-node src/helper/report/report.ts",
     "test:failed": "cucumber-js -p rerun @rerun.txt",
     "lint": "eslint 'src/**/*.ts' --fix"

e2e-playwright/src/features/Brokers.feature

@@ -0,0 +1,31 @@
+Feature: Brokers page
+
+  Scenario: Brokers visibility BrokerDetails visibility
+      Given Brokers is visible
+      When click on Brokers link
+      Then Brokers heading visible
+      Then the end of current URL should be "brokers"
+      Given Brokers Uptime visible is: "true"
+      Given Brokers Partitions visible is: "true"
+      When Brokers cell element "1" clicked
+      Given BrokerDetails name is: "BrokersBroker" header visible is: "true"
+      Given BrokerDetails Log directories visible is: "true"
+      Given BrokerDetails Configs visible is: "true"
+      Given BrokerDetails Metrics visible is: "true"
+
+  Scenario: Brokers visibility BrokerDetails visibility
+      Given Brokers is visible
+      When click on Brokers link
+      Then Brokers heading visible
+      Then the end of current URL should be "brokers"
+      Given Brokers Uptime visible is: "true"
+      Given Brokers Partitions visible is: "true"
+      When Brokers cell element "1" clicked
+      Given BrokerDetails name is: "BrokersBroker" header visible is: "true"
+      When BrokerDetails Configs clicked
+      Given BrokerDetails Configs Key visible is: "true"
+      Given BrokerDetails Configs Value visible is: "true"
+      Given BrokerDetails Configs Source visible is: "true"
+      Then BrokerDetails searchfield visible is: "true"
+      When BrokerDetails searchfield input is: "process.roles" cell value is: "broker,controller"
+      When BrokerDetails searchfield input is: "broker,controller" cell value is: "process.roles"

e2e-playwright/src/features/KsqlDb.feature

@@ -0,0 +1,84 @@
+Feature: Ksqldb page visibility
+
+  Scenario: KSQL DB elements visibility
+    Given KSQL DB is visible
+    When click on KSQL DB link
+    Then KSQL DB heading visible
+    Then the part of current URL should be "ksqldb"
+    Given KSQL DB Tables header visible is: "true"
+    Given KSQL DB Streams header visible is: "true"
+    Given KSQL DB Tables link visible is: "true"
+    Given KSQL DB Streams link visible is: "true"
+    When KSQL DB ExecuteKSQLRequest click
+    Given KSQL DB Clear visible is: "true"
+    Given KSQL DB Execute visible is: "true"
+
+  Scenario: KSQL DB queries clear result
+    Given KSQL DB is visible
+    When click on KSQL DB link
+    Then KSQL DB heading visible
+    Then the part of current URL should be "ksqldb"
+    Given KSQL DB Tables header visible is: "true"
+    Given KSQL DB Streams header visible is: "true"
+    Given KSQL DB Tables link visible is: "true"
+    Given KSQL DB Streams link visible is: "true"
+    When KSQL DB ExecuteKSQLRequest click
+    Given KSQL DB textbox visible is: "true"
+    Given KSQL DB KSQL for stream starts with: "STREAM_ONE", kafka_topic starts with: "NewAutoTopic", value_format: "json"
+    Then KSQL DB stream created
+    Then KSQL DB clear result visible is: "true"
+
+  Scenario: KSQL DB queries
+    Given KSQL DB is visible
+    When click on KSQL DB link
+    Then KSQL DB heading visible
+    Then the part of current URL should be "ksqldb"
+    Given KSQL DB Tables header visible is: "true"
+    Given KSQL DB Streams header visible is: "true"
+    Given KSQL DB Tables link visible is: "true"
+    Given KSQL DB Streams link visible is: "true"
+    When KSQL DB ExecuteKSQLRequest click
+    Given KSQL DB textbox visible is: "true"
+    Given KSQL DB KSQL for stream starts with: "STREAM_ONE", kafka_topic starts with: "NewAutoTopic", value_format: "json"
+    Then KSQL DB stream created
+    When KSQL DB Stream clicked
+    Then KSQL DB stream starts with: "STREAM_ONE" visible is: "true"
+    When KSQL DB ExecuteKSQLRequest click
+    Given KSQL DB textbox visible is: "true"
+    Then KSQL DB KSQL for table starts with: "TABLE_ONE", stream starts with: "STREAM_ONE"
+    Then KSQL DB table created
+    When KSQL DB Table clicked
+    Then KSQL DB table starts with: "TABLE_ONE" visible is: "true"
+
+  Scenario: KSQL DB cancel queries
+    Given KSQL DB is visible
+    When click on KSQL DB link
+    Then KSQL DB heading visible
+    Then the part of current URL should be "ksqldb"
+    Given KSQL DB Tables header visible is: "true"
+    Given KSQL DB Streams header visible is: "true"
+    Given KSQL DB Tables link visible is: "true"
+    Given KSQL DB Streams link visible is: "true"
+    When KSQL DB ExecuteKSQLRequest click
+    Given KSQL DB textbox visible is: "true"
+    Given KSQL DB KSQL for stream starts with: "STREAM_ONE", kafka_topic starts with: "NewAutoTopic", value_format: "json"
+    Then KSQL DB stream created
+    Then KSQL DB KSQL cleared
+    When KSQL DB ExecuteKSQLRequest click
+    Given KSQL DB textbox visible is: "true"
+    Then KSQL DB KSQL for table starts with: "TABLE_ONE", stream starts with: "STREAM_ONE"
+    Then KSQL DB table created
+    Then KSQL DB KSQL cleared
+    When KSQL DB ExecuteKSQLRequest click
+    Given KSQL DB textbox visible is: "true"
+    Given KSQL DB KSQL data inserted to stream starts with: "STREAM_ONE", from table:
+    |Id         |la        |lo          |
+    | c2309eec  | 37.7877  | -122.4205  |
+    | 18f4ea86  | 37.3903  | -122.0643  |
+    | 4ab5cbad  | 37.3952  | -122.0813  |
+    | 8b6eae59  | 37.3944  | -122.0813  |
+    | 4a7c7b41  | 37.4049  | -122.0822  |
+    | 4ddad000  | 37.7857  | -122.4011  |
+
+    Given KSQL DB long query stream starts with: "STREAM_ONE" stared
+    Given KSQL DB long query stoped

e2e-playwright/src/features/SchemaRegistry.feature

@@ -0,0 +1,84 @@
+Feature: Schema page
+
+  Scenario: SchemaRegistry and SchemaRegistryCreate visibility
+    Given Schema Registry is visible
+    When click on Schema Registry link
+    Then Schema Registry heading visible
+    Given SchemaRegistry CheateSchema clicked
+    Given SchemaRegistryCreate is visible
+    Given SchemaRegistryCreate Subject visible is: "true"
+    Given SchemaRegistryCreate Schema visible is: "true"
+    Given SchemaRegistryCreate SchemaType visible is: "true"
+    When SchemaRegistryCreate Subject input starts with: "SchemaSubject"
+    When SchemaRegistryCreate Schema input from avro
+    When SchemaRegistryCreate Submit clicked
+    Then SchemaRegistrySchemaName starts with: "SchemaSubject", visible is: "true"
+
+  Scenario: SchemaRegistry Avro schema actions
+    Given Schema Registry is visible
+    When click on Schema Registry link
+    Then Schema Registry heading visible
+    Given SchemaRegistry CheateSchema clicked
+    Given SchemaRegistryCreate is visible
+    Given SchemaRegistryCreate Subject visible is: "true"
+    Given SchemaRegistryCreate Schema visible is: "true"
+    Given SchemaRegistryCreate SchemaType visible is: "true"
+    When SchemaRegistryCreate Subject input starts with: "SchemaSubject"
+    When SchemaRegistryCreate Schema input from avro
+    When SchemaRegistryCreate Submit clicked
+    Then SchemaRegistrySchemaName starts with: "SchemaSubject", visible is: "true"
+    When click on Brokers link
+    When click on Schema Registry link
+    Given SchemaRegistry click on schema starts with: "SchemaSubject"
+    Given SchemaRegistrySchemaName version is: "1"
+    Given SchemaRegistrySchemaName type is: "AVRO"
+    Given SchemaRegistrySchemaName Compatibility is: "BACKWARD"
+    When SchemaRegistrySchemaName remove schema clicked
+    Then Schema starts with: "SchemaSubject" deleted
+    Then SchemaRegistrySchemaName starts with: "SchemaSubject", visible is: "false"
+
+  Scenario: SchemaRegistry Json schema actions
+    Given Schema Registry is visible
+    When click on Schema Registry link
+    Then Schema Registry heading visible
+    Given SchemaRegistry CheateSchema clicked
+    Given SchemaRegistryCreate is visible
+    Given SchemaRegistryCreate Subject visible is: "true"
+    Given SchemaRegistryCreate Schema visible is: "true"
+    Given SchemaRegistryCreate SchemaType visible is: "true"
+    When SchemaRegistryCreate Subject input starts with: "SchemaSubject"
+    When SchemaRegistryCreate Schema input from json
+    When SchemaRegistryCreate Submit clicked
+    Then SchemaRegistrySchemaName starts with: "SchemaSubject", visible is: "true"
+    When click on Brokers link
+    When click on Schema Registry link
+    Given SchemaRegistry click on schema starts with: "SchemaSubject"
+    Given SchemaRegistrySchemaName version is: "1"
+    Given SchemaRegistrySchemaName type is: "JSON"
+    Given SchemaRegistrySchemaName Compatibility is: "BACKWARD"
+    When SchemaRegistrySchemaName remove schema clicked
+    Then Schema starts with: "SchemaSubject" deleted
+    Then SchemaRegistrySchemaName starts with: "SchemaSubject", visible is: "false"
+
+  Scenario: SchemaRegistry Json schema actions
+    Given Schema Registry is visible
+    When click on Schema Registry link
+    Then Schema Registry heading visible
+    Given SchemaRegistry CheateSchema clicked
+    Given SchemaRegistryCreate is visible
+    Given SchemaRegistryCreate Subject visible is: "true"
+    Given SchemaRegistryCreate Schema visible is: "true"
+    Given SchemaRegistryCreate SchemaType visible is: "true"
+    When SchemaRegistryCreate Subject input starts with: "SchemaSubject"
+    When SchemaRegistryCreate Schema input from protobuf
+    When SchemaRegistryCreate Submit clicked
+    Then SchemaRegistrySchemaName starts with: "SchemaSubject", visible is: "true"
+    When click on Brokers link
+    When click on Schema Registry link
+    Given SchemaRegistry click on schema starts with: "SchemaSubject"
+    Given SchemaRegistrySchemaName version is: "1"
+    Given SchemaRegistrySchemaName type is: "PROTOBUF"
+    Given SchemaRegistrySchemaName Compatibility is: "BACKWARD"
+    When SchemaRegistrySchemaName remove schema clicked
+    Then Schema starts with: "SchemaSubject" deleted
+    Then SchemaRegistrySchemaName starts with: "SchemaSubject", visible is: "false"

e2e-playwright/src/features/TopicsCreate.feature → e2e-playwright/src/features/TopicsActions.feature

@@ -51,3 +51,19 @@ Feature: TopicsCreate page
     Then TopicCreate TimeToRetainData value is: "604800000"
     When TopicCreate 4Weeks button clicked
     Then TopicCreate TimeToRetainData value is: "2419200000"
+
+  Scenario: Topic Delete
+    Given Topics is visible
+    When click on Topics link
+    Given Topics AddATopic clicked
+    Given TopicCreate heading visible is: "true"
+    When TopicCreate Topic name starts with: "NewAutoTopic"
+    When TopicCreate Number of partitons: 1
+    When TopicCreate Time to retain data one day
+    When TopicCreate Create topic clicked
+    Then Header starts with: "NewAutoTopic"
+    When click on Topics link
+    Then Topic name started with: "NewAutoTopic" visible is: "true"
+    When Topic name started with: "NewAutoTopic" RemoveTopic clicked
+    Then Topic name started with: "NewAutoTopic" visible is: "false"
+