| Safe Haskell | None |
|---|---|
| Language | GHC2021 |
Test.FeatureFlags.MeetingPremium
Synopsis
- testPatchMeetingPremium :: HasCallStack => App ()
- testMeetingPremium :: HasCallStack => APIAccess -> App ()
- testMeetingPremiumRemovedAtV17 :: HasCallStack => App ()
- testMeetingPremiumListedAtV17 :: HasCallStack => App ()
Documentation
testPatchMeetingPremium :: HasCallStack => App () Source #
testMeetingPremium :: HasCallStack => APIAccess -> App () Source #
testMeetingPremiumRemovedAtV17 :: HasCallStack => App () Source #
WPB-26771: the public meetingsPremium endpoints are gated at v17 (404)
while remaining available through v16. Only the v16 GET is asserted here:
v16 PUT success is covered by testMeetingPremium (whose runFeatureTests
unlocks the feature first), and a public PUT in this test would 409
feature-locked against the default enabled+locked state.
testMeetingPremiumListedAtV17 :: HasCallStack => App () Source #
WPB-26771: the aggregate list endpoints 'GET /feature-configs' and
'GET teams:tid/features' are version-agnostic — like From-gated features
(e.g. MLS), they include every feature at every API version. Even though the
dedicated meetingsPremium endpoints 404 at v17, both list endpoints keep
returning the (default enabled+locked) meetingsPremium entry. This test
locks that behaviour in.