Skip to content

Commit 6ec2c5b

Browse files
committed
update test to reflect changed behavior #909
1 parent ac39ae5 commit 6ec2c5b

File tree

1 file changed

+2
-12
lines changed

1 file changed

+2
-12
lines changed

test-files/ui/features/z_conflate_export_osm_api_db.feature

Lines changed: 2 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -9,17 +9,7 @@ Feature: Conflate and Export OSM API Database Dataset
99
And I press "Add Layer"
1010
Then I wait 30 "seconds" to see "DcTigerRoadsCucumber"
1111
And I press "Add Secondary Dataset"
12-
And I click the "OSM_API_DB_osmapi_test" Dataset
13-
And I press "Add Layer"
14-
Then I wait 30 "seconds" to see "OSM_API_DB_osmapi_test"
15-
Then I wait 30 "seconds" to see "Conflate"
16-
And I press "Conflate"
17-
And I scroll element into view and press "conflate2"
18-
# I couldn't figure out how to do a "wait to see" step def for an alert...if possible, would speed this
19-
# and the other ones like it in this file up quite a bit.
20-
And I wait 30 seconds
21-
Then I should see an alert containing "OSM API database not allowed as secondary layer input"
22-
Then I accept the alert
12+
And I should not see "OSM_API_DB_osmapi_test"
2313

2414
Scenario: Conflate an OSM API Database Dataset with a Hootenanny Dataset and Export the Conflated Result Back Into the OSM API Database
2515
Given I am on Hootenanny
@@ -36,7 +26,7 @@ Feature: Conflate and Export OSM API Database Dataset
3626
Then I wait 30 "seconds" to see "Conflate"
3727
And I press "Conflate"
3828
And I scroll element into view and press "conflate2"
39-
Then I wait 30 "seconds" to see "Conflating …"
29+
Then I wait 60 "seconds" to see "Conflating …"
4030
Then I wait 3 "minutes" to see "osmapi_test_AllDataTypesBCucumber"
4131
Then I should see "Complete Review"
4232
Then I wait 30 "seconds" to see "Reviews remaining:"

0 commit comments

Comments
 (0)