Skip to content

Commit a4fc534

Browse files
germanosingermanosin
authored
Merge branch 'main' into issue/233
2 parents 34ff202 + 5b09e54 commit a4fc534

29 files changed

+1247
-3
lines changed

‎e2e-playwright/config/cucumber.js‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
/* eslint-disable */
22
module.exports = {
33
default: {
4-
timeout: 30000,
4+
timeout: 60000,
55
tags: process.env.npm_config_TAGS || "",
66
formatOptions: {
77
snippetInterface: "async-await"

‎e2e-playwright/package.json‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@
77
"pretest": "npx ts-node src/helper/report/init.ts",
88
"test": "cross-env ENV=prod FORCE_COLOR=0 cucumber-js --config=config/cucumber.js",
99
"test:stage": "cross-env ENV=stage FORCE_COLOR=0 cucumber-js --config=config/cucumber.js",
10+
"test:sp": "cross-env ENV=stage FORCE_COLOR=0 cucumber-js --config=config/cucumber.js --tags @sp",
1011
"posttest": "npx ts-node src/helper/report/report.ts",
1112
"test:failed": "cucumber-js -p rerun @rerun.txt",
1213
"lint": "eslint 'src/**/*.ts' --fix"

‎e2e-playwright/src/features/Brokers.feature‎

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
Feature: Brokers page
2+
3+
Scenario: Brokers visibility BrokerDetails visibility
4+
Given Brokers is visible
5+
When click on Brokers link
6+
Then Brokers heading visible
7+
Then the end of current URL should be "brokers"
8+
Given Brokers Uptime visible is: "true"
9+
Given Brokers Partitions visible is: "true"
10+
When Brokers cell element "1" clicked
11+
Given BrokerDetails name is: "BrokersBroker" header visible is: "true"
12+
Given BrokerDetails Log directories visible is: "true"
13+
Given BrokerDetails Configs visible is: "true"
14+
Given BrokerDetails Metrics visible is: "true"
15+
16+
Scenario: Brokers visibility BrokerDetails visibility
17+
Given Brokers is visible
18+
When click on Brokers link
19+
Then Brokers heading visible
20+
Then the end of current URL should be "brokers"
21+
Given Brokers Uptime visible is: "true"
22+
Given Brokers Partitions visible is: "true"
23+
When Brokers cell element "1" clicked
24+
Given BrokerDetails name is: "BrokersBroker" header visible is: "true"
25+
When BrokerDetails Configs clicked
26+
Given BrokerDetails Configs Key visible is: "true"
27+
Given BrokerDetails Configs Value visible is: "true"
28+
Given BrokerDetails Configs Source visible is: "true"
29+
Then BrokerDetails searchfield visible is: "true"
30+
When BrokerDetails searchfield input is: "process.roles" cell value is: "broker,controller"
31+
When BrokerDetails searchfield input is: "broker,controller" cell value is: "process.roles"

‎e2e-playwright/src/features/KsqlDb.feature‎

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
Feature: Ksqldb page visibility
2+
3+
Scenario: KSQL DB elements visibility
4+
Given KSQL DB is visible
5+
When click on KSQL DB link
6+
Then KSQL DB heading visible
7+
Then the part of current URL should be "ksqldb"
8+
Given KSQL DB Tables header visible is: "true"
9+
Given KSQL DB Streams header visible is: "true"
10+
Given KSQL DB Tables link visible is: "true"
11+
Given KSQL DB Streams link visible is: "true"
12+
When KSQL DB ExecuteKSQLRequest click
13+
Given KSQL DB Clear visible is: "true"
14+
Given KSQL DB Execute visible is: "true"
15+
16+
Scenario: KSQL DB queries clear result
17+
Given KSQL DB is visible
18+
When click on KSQL DB link
19+
Then KSQL DB heading visible
20+
Then the part of current URL should be "ksqldb"
21+
Given KSQL DB Tables header visible is: "true"
22+
Given KSQL DB Streams header visible is: "true"
23+
Given KSQL DB Tables link visible is: "true"
24+
Given KSQL DB Streams link visible is: "true"
25+
When KSQL DB ExecuteKSQLRequest click
26+
Given KSQL DB textbox visible is: "true"
27+
Given KSQL DB KSQL for stream starts with: "STREAM_ONE", kafka_topic starts with: "NewAutoTopic", value_format: "json"
28+
Then KSQL DB stream created
29+
Then KSQL DB clear result visible is: "true"
30+
31+
Scenario: KSQL DB queries
32+
Given KSQL DB is visible
33+
When click on KSQL DB link
34+
Then KSQL DB heading visible
35+
Then the part of current URL should be "ksqldb"
36+
Given KSQL DB Tables header visible is: "true"
37+
Given KSQL DB Streams header visible is: "true"
38+
Given KSQL DB Tables link visible is: "true"
39+
Given KSQL DB Streams link visible is: "true"
40+
When KSQL DB ExecuteKSQLRequest click
41+
Given KSQL DB textbox visible is: "true"
42+
Given KSQL DB KSQL for stream starts with: "STREAM_ONE", kafka_topic starts with: "NewAutoTopic", value_format: "json"
43+
Then KSQL DB stream created
44+
When KSQL DB Stream clicked
45+
Then KSQL DB stream starts with: "STREAM_ONE" visible is: "true"
46+
When KSQL DB ExecuteKSQLRequest click
47+
Given KSQL DB textbox visible is: "true"
48+
Then KSQL DB KSQL for table starts with: "TABLE_ONE", stream starts with: "STREAM_ONE"
49+
Then KSQL DB table created
50+
When KSQL DB Table clicked
51+
Then KSQL DB table starts with: "TABLE_ONE" visible is: "true"
52+
53+
Scenario: KSQL DB cancel queries
54+
Given KSQL DB is visible
55+
When click on KSQL DB link
56+
Then KSQL DB heading visible
57+
Then the part of current URL should be "ksqldb"
58+
Given KSQL DB Tables header visible is: "true"
59+
Given KSQL DB Streams header visible is: "true"
60+
Given KSQL DB Tables link visible is: "true"
61+
Given KSQL DB Streams link visible is: "true"
62+
When KSQL DB ExecuteKSQLRequest click
63+
Given KSQL DB textbox visible is: "true"
64+
Given KSQL DB KSQL for stream starts with: "STREAM_ONE", kafka_topic starts with: "NewAutoTopic", value_format: "json"
65+
Then KSQL DB stream created
66+
Then KSQL DB KSQL cleared
67+
When KSQL DB ExecuteKSQLRequest click
68+
Given KSQL DB textbox visible is: "true"
69+
Then KSQL DB KSQL for table starts with: "TABLE_ONE", stream starts with: "STREAM_ONE"
70+
Then KSQL DB table created
71+
Then KSQL DB KSQL cleared
72+
When KSQL DB ExecuteKSQLRequest click
73+
Given KSQL DB textbox visible is: "true"
74+
Given KSQL DB KSQL data inserted to stream starts with: "STREAM_ONE", from table:
75+
|Id |la |lo |
76+
| c2309eec | 37.7877 | -122.4205 |
77+
| 18f4ea86 | 37.3903 | -122.0643 |
78+
| 4ab5cbad | 37.3952 | -122.0813 |
79+
| 8b6eae59 | 37.3944 | -122.0813 |
80+
| 4a7c7b41 | 37.4049 | -122.0822 |
81+
| 4ddad000 | 37.7857 | -122.4011 |
82+
83+
Given KSQL DB long query stream starts with: "STREAM_ONE" stared
84+
Given KSQL DB long query stoped

‎e2e-playwright/src/features/SchemaRegistry.feature‎

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
Feature: Schema page
2+
3+
Scenario: SchemaRegistry and SchemaRegistryCreate visibility
4+
Given Schema Registry is visible
5+
When click on Schema Registry link
6+
Then Schema Registry heading visible
7+
Given SchemaRegistry CheateSchema clicked
8+
Given SchemaRegistryCreate is visible
9+
Given SchemaRegistryCreate Subject visible is: "true"
10+
Given SchemaRegistryCreate Schema visible is: "true"
11+
Given SchemaRegistryCreate SchemaType visible is: "true"
12+
When SchemaRegistryCreate Subject input starts with: "SchemaSubject"
13+
When SchemaRegistryCreate Schema input from avro
14+
When SchemaRegistryCreate Submit clicked
15+
Then SchemaRegistrySchemaName starts with: "SchemaSubject", visible is: "true"
16+
17+
Scenario: SchemaRegistry Avro schema actions
18+
Given Schema Registry is visible
19+
When click on Schema Registry link
20+
Then Schema Registry heading visible
21+
Given SchemaRegistry CheateSchema clicked
22+
Given SchemaRegistryCreate is visible
23+
Given SchemaRegistryCreate Subject visible is: "true"
24+
Given SchemaRegistryCreate Schema visible is: "true"
25+
Given SchemaRegistryCreate SchemaType visible is: "true"
26+
When SchemaRegistryCreate Subject input starts with: "SchemaSubject"
27+
When SchemaRegistryCreate Schema input from avro
28+
When SchemaRegistryCreate Submit clicked
29+
Then SchemaRegistrySchemaName starts with: "SchemaSubject", visible is: "true"
30+
When click on Brokers link
31+
When click on Schema Registry link
32+
Given SchemaRegistry click on schema starts with: "SchemaSubject"
33+
Given SchemaRegistrySchemaName version is: "1"
34+
Given SchemaRegistrySchemaName type is: "AVRO"
35+
Given SchemaRegistrySchemaName Compatibility is: "BACKWARD"
36+
When SchemaRegistrySchemaName remove schema clicked
37+
Then Schema starts with: "SchemaSubject" deleted
38+
Then SchemaRegistrySchemaName starts with: "SchemaSubject", visible is: "false"
39+
40+
Scenario: SchemaRegistry Json schema actions
41+
Given Schema Registry is visible
42+
When click on Schema Registry link
43+
Then Schema Registry heading visible
44+
Given SchemaRegistry CheateSchema clicked
45+
Given SchemaRegistryCreate is visible
46+
Given SchemaRegistryCreate Subject visible is: "true"
47+
Given SchemaRegistryCreate Schema visible is: "true"
48+
Given SchemaRegistryCreate SchemaType visible is: "true"
49+
When SchemaRegistryCreate Subject input starts with: "SchemaSubject"
50+
When SchemaRegistryCreate Schema input from json
51+
When SchemaRegistryCreate Submit clicked
52+
Then SchemaRegistrySchemaName starts with: "SchemaSubject", visible is: "true"
53+
When click on Brokers link
54+
When click on Schema Registry link
55+
Given SchemaRegistry click on schema starts with: "SchemaSubject"
56+
Given SchemaRegistrySchemaName version is: "1"
57+
Given SchemaRegistrySchemaName type is: "JSON"
58+
Given SchemaRegistrySchemaName Compatibility is: "BACKWARD"
59+
When SchemaRegistrySchemaName remove schema clicked
60+
Then Schema starts with: "SchemaSubject" deleted
61+
Then SchemaRegistrySchemaName starts with: "SchemaSubject", visible is: "false"
62+
63+
Scenario: SchemaRegistry Json schema actions
64+
Given Schema Registry is visible
65+
When click on Schema Registry link
66+
Then Schema Registry heading visible
67+
Given SchemaRegistry CheateSchema clicked
68+
Given SchemaRegistryCreate is visible
69+
Given SchemaRegistryCreate Subject visible is: "true"
70+
Given SchemaRegistryCreate Schema visible is: "true"
71+
Given SchemaRegistryCreate SchemaType visible is: "true"
72+
When SchemaRegistryCreate Subject input starts with: "SchemaSubject"
73+
When SchemaRegistryCreate Schema input from protobuf
74+
When SchemaRegistryCreate Submit clicked
75+
Then SchemaRegistrySchemaName starts with: "SchemaSubject", visible is: "true"
76+
When click on Brokers link
77+
When click on Schema Registry link
78+
Given SchemaRegistry click on schema starts with: "SchemaSubject"
79+
Given SchemaRegistrySchemaName version is: "1"
80+
Given SchemaRegistrySchemaName type is: "PROTOBUF"
81+
Given SchemaRegistrySchemaName Compatibility is: "BACKWARD"
82+
When SchemaRegistrySchemaName remove schema clicked
83+
Then Schema starts with: "SchemaSubject" deleted
84+
Then SchemaRegistrySchemaName starts with: "SchemaSubject", visible is: "false"

‎e2e-playwright/src/features/TopicsCreate.feature‎ renamed to ‎e2e-playwright/src/features/TopicsActions.feature‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,3 +51,19 @@ Feature: TopicsCreate page
5151
Then TopicCreate TimeToRetainData value is: "604800000"
5252
When TopicCreate 4Weeks button clicked
5353
Then TopicCreate TimeToRetainData value is: "2419200000"
54+
55+
Scenario: Topic Delete
56+
Given Topics is visible
57+
When click on Topics link
58+
Given Topics AddATopic clicked
59+
Given TopicCreate heading visible is: "true"
60+
When TopicCreate Topic name starts with: "NewAutoTopic"
61+
When TopicCreate Number of partitons: 1
62+
When TopicCreate Time to retain data one day
63+
When TopicCreate Create topic clicked
64+
Then Header starts with: "NewAutoTopic"
65+
When click on Topics link
66+
Then Topic name started with: "NewAutoTopic" visible is: "true"
67+
When Topic name started with: "NewAutoTopic" RemoveTopic clicked
68+
Then Topic name started with: "NewAutoTopic" visible is: "false"
69+

0 commit comments

Comments
 (0)