relate feature issue
relate status-go implementation that can be referrenced.
relate status-mobile commit id: 7b425c1a5301996afa28a079c159c80f952e05c3
User Story
As a QA automation engineer, I require the ability to utilize UI buttons within the e2e builds to instantaneously generate three distinct types of communities. This feature will significantly enhance the speed and efficiency of automation testing by utilizing frontend code to call upon status-go backend services.
Description
Closed Community
Name: closed community
Description: A private community designed to verify membership requests.
Logo: Any suitable image.
Banner: Any suitable image.
Colour: #887af9
Community history service: Enabled
Request to join: Required
Any member can pin a message: Yes
Channels:
general (no category)
cats (category: pets)
dogs (category: pets)
rules (category: household)
Categories: pets, household
Open Community
Name: open community
Description: An accessible community allowing free join without requests.
Logo: Any suitable image.
Banner: Any suitable image.
Colour: #26a69a
Community history service: Enabled
Request to join: Not required
Any member can pin a message: No
Token-gated Community
Name: SNT community
Description: Entry requires holding 10 SNT on the Goerli network.
Logo: Any suitable image.
Banner: Any suitable image.
Colour: #eab700
Community history service: Enabled
Request to join: Required
Any member can pin a message: No
PERMISSIONS: Holding 10 SNT on the Goerli network is a prerequisite for membership.
Acceptance Criteria
The e2e and PR build environments must include three buttons, each dedicated to the creation of one of the specified community types using frontend code to invoke backend services, thereby streamlining the testing process for QA automation.
qfrank
commented
9 months ago
Feature Issue
Add methods for fast creation of communities only on status-mobile side with combination of invoking exist backend
API, e.g. CreateCommunity / CreateCommunityChat / CreateCommunityCategorythe code in status-go implementation will be removed once this feature is implemented on
status-mobileside to apply these comments: comment1 / comment2.relate feature issue relate status-go implementation that can be referrenced. relate status-mobile commit id:
7b425c1a5301996afa28a079c159c80f952e05c3User Story
As a QA automation engineer, I require the ability to utilize UI buttons within the e2e builds to instantaneously generate three distinct types of communities. This feature will significantly enhance the speed and efficiency of automation testing by utilizing frontend code to call upon status-go backend services.
Description
Closed Community
Name: closed community Description: A private community designed to verify membership requests. Logo: Any suitable image. Banner: Any suitable image. Colour: #887af9 Community history service: Enabled Request to join: Required Any member can pin a message: Yes Channels:
general (no category)
cats (category: pets)
dogs (category: pets)
rules (category: household)
Categories: pets, household
Open Community
Name: open community Description: An accessible community allowing free join without requests. Logo: Any suitable image. Banner: Any suitable image. Colour: #26a69a Community history service: Enabled Request to join: Not required Any member can pin a message: No
Token-gated Community
Name: SNT community Description: Entry requires holding 10 SNT on the Goerli network. Logo: Any suitable image. Banner: Any suitable image. Colour: #eab700 Community history service: Enabled Request to join: Required Any member can pin a message: No PERMISSIONS: Holding 10 SNT on the Goerli network is a prerequisite for membership.
Acceptance Criteria
The e2e and PR build environments must include three buttons, each dedicated to the creation of one of the specified community types using frontend code to invoke backend services, thereby streamlining the testing process for QA automation.