Content Publishing in test should not be counted against the Limits allocated - Ideas - Salesforce Trailblazer Community
Trailblazer Community

All Ideas

Idea Details

Post an Idea
40  Points
Idea has been posted. Give it an upvote or downvote.

Content Publishing in test should not be counted against the Limits allocated

CMS & Websites

The content publishing in test runs are counted against the limits bandwidth allocated to our instance. The situation is even worse when it comes to sandboxes, because limit is further reduced on the sandboxes. And obviously we want to test each and every functionality of the instance and not to behave differently in the test context hence, we have to publish the content in the test cases (Also, there is no way to mock in test cases).
Following are the challenges
- CI/CD pipelines continuously fails for the lower environments since the limit is really low.
- Each time a refresh is done, need to create a case with salesforce to get it increased with a business justification.
- Developer teams get blocked sometimes to further deliver the user stories.
- Lower instances behave way differently than the production.
- Running validate against production for each user story in lower environment may be costlier - since it will utilize limts

Resolution Recommendations:
- ideally salesforce should not count test runs as limit
- A way to mock the publishing content like we do for APIs
- Production and staging should be as close as possible

Ref article: 

Merge Idea · Flag

  • Upvotes
  • Downvotes



from AppExchange


Help us to keep IdeaExchange clean by pointing out overlapping ideas. We'll investigate your suggestion and merge the ideas if it makes sense.



Thanks for your merge suggestion. We will review it shortly and merge the ideas if applicable.

Salesforce takes abuse situations very seriously. Examples of abuse include but are not limited to posting of offensive language or fraudulent statements. To help us process your request as quickly as possible, please fill out the form below describing the situation. For privacy and security reasons, the final outcome of an abuse case may not be revealed to the person who reported it.


Thank you for your feedback. We take abuse seriously and will investigate this issue and take appropriate action.