Skip to content

Commit bc45053

Browse files
authored
Merge pull request #774 from bcgov/ricander
Ricander
2 parents 86fd52c + 103118f commit bc45053

28 files changed

+1557
-38
lines changed
Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
Feature: ManagePlatformsAddPlatform
2+
Link to a feature: https://hous-hpb.atlassian.net/browse/DSS-226
3+
4+
@AddPlatform
5+
Scenario: AddPlatform
6+
#User Authentication
7+
Given that I am an authenticated User "<UserName>" and the expected result is "<ExpectedResult>" and I am a "<UserType>" user
8+
Then I am directed to the Landing Page
9+
10+
#Select Manage Platforms
11+
When I login and navigate to the Manage Platforms feature
12+
13+
Then I should be presented with a list of platforms and sub-platforms
14+
15+
#Select Platform
16+
When I click the add new platform button for a platform
17+
18+
#Add platform
19+
20+
Then I should be presented with the Add Platform page
21+
22+
#Input fields
23+
Then I should see a form with the required input fields for creating a sub-platform
24+
25+
#Platform Name
26+
#Platform Code
27+
#Primary Email for Non-Compliance Notices
28+
#Primary Email for Takedown Request Letters
29+
#Secondary Email for Non-Compliance Notices
30+
#Secondary Email for Takedown Request Letters
31+
#Platform Type
32+
#Platform Status
33+
34+
35+
#Enter values for Input Fields
36+
When I fill in valid values for the input fields
37+
Then the Save button should be enabled
38+
39+
#Click Save button to create sub platform
40+
When I click the Save button
41+
Then the sub platform should be created
42+
Then the sub platform should be a child of the parent platform
43+
44+
45+
46+
Examples:
47+
| UserName | UserType | Environment | ExpectedResult |
48+
| CEUATST | ceu_admin | all | pass |
49+
50+
51+
52+
53+
54+

Test/UITest/SpecFlowProjectBDD/Features/AddPlatform.feature.cs

Lines changed: 148 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

Test/UITest/SpecFlowProjectBDD/Features/AddSubsidiaryPlatform.feature

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
Feature: ManagePlatforms
1+
Feature: ManagePlatformsAddSubPlatform
22
Link to a feature: https://hous-hpb.atlassian.net/browse/DSS-226
33

44
@AddSubsidiaryPlatform

Test/UITest/SpecFlowProjectBDD/Features/AddSubsidiaryPlatform.feature.cs

Lines changed: 3 additions & 3 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
Feature: ManagePlatformsEditPlatform
2+
Link to a feature: https://hous-hpb.atlassian.net/browse/DSS-226
3+
4+
@EditPlatform
5+
Scenario: EditPlatform
6+
#User Authentication
7+
Given that I am an authenticated User "<UserName>" and the expected result is "<ExpectedResult>" and I am a "<UserType>" user
8+
Then I am directed to the Landing Page
9+
10+
#Select Manage Platforms
11+
When I click on the Manage Platforms button
12+
Then I should be presented with a list of platforms and sub-platforms
13+
14+
#Select Platform
15+
When I select an existing platform
16+
Then I should be be able to edit platform information,
17+
And I should see a call to action to disable the platform
18+
19+
#Edit sub-platform Name
20+
When I edit platform name information
21+
Then platform information should update across the platform (e.g., listing view, detailed view, and drop down platform select menus, etc.)
22+
23+
#Edit sub-platform Contacts
24+
When I edit platform email addresses
25+
Then emails should go to the updated platform contacts for each type of email (Notice, takedown,)
26+
27+
#Edit Platform Parent, Subsidiary or Code
28+
When I update parent or subsidiary information or platform code
29+
Then the platform should be able to upload monthly data reports or takedown reports for all platforms associated with it (ie. parent or subsidiary platforms)
30+
And the platform uploads should validate against the updated platform code
31+
32+
#Input fields
33+
# Then I should see a form with the required input fields for creating a sub-platform
34+
#
35+
# #Platform Name
36+
# #Platform Code
37+
# #Primary Email for Non-Compliance Notices
38+
# #Primary Email for Takedown Request Letters
39+
# #Secondary Email for Non-Compliance Notices
40+
# #Secondary Email for Takedown Request Letters
41+
42+
43+
#Error Handling:
44+
When submitting platform details
45+
Then the system should perform validation checks and provide clear error messages for any input errors
46+
47+
#Click Save button to create sub platform
48+
When I click the Save button
49+
Then the sub platform should be created
50+
Then the sub platform should be a child of the parent platform
51+
52+
Examples:
53+
| UserName | UserType | Environment | ExpectedResult |
54+
| CEUATST | ceu_admin | all | pass |
55+
56+
57+
58+
59+
60+

0 commit comments

Comments
 (0)