Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add tests for the most important functions of ButterCMS #39

Open
LukaszGudel opened this issue Sep 27, 2024 · 0 comments
Open

Add tests for the most important functions of ButterCMS #39

LukaszGudel opened this issue Sep 27, 2024 · 0 comments

Comments

@LukaszGudel
Copy link
Collaborator

Why

Because current tests moved from the StatusCake test only super simple cases probably cached by CDN.

What

Add tests to CKSMonitoring that more deeply check whether the most important system functions are working (most important from the customers’ point of view)

Below are examples of such parts:

  • Dashboard (logging in, and then making sure the internal endpoints work)
  • API endpoints
  • Being able to update a piece of content and then see the change in the API
  • Sign up
  • Billing would be great, but probably not possible to test fully

Important info:

  • Of course, we should add tests we are able to do using API and HTTP client (without using browser/puppeteer) - they should be quite fast (not longer than 5s)
  • we need to be careful not to clutter the Butter database and affect its performance

Link to discussion on Slack: https://cksource.slack.com/archives/C0747MQGE2W/p1725011401287559


Definition of Ready

  • Defined and understandable (Is there a common understanding amongst the team on what the task is and how it will be implemented?)
  • Estimated (Has the task been estimated by the team? And, is the item agreed to be of a size that the team are comfortable can be completed within an iteration?)
  • Testable/demonstrable (Do the team understand how they can test or demonstrate the task or discuss it in the sprint review once complete?)
  • Actionable/Executable/Unblocked (Can this task be done? Are there no other blockers/obstacles?)

Definition of Done

  • Automatically tested (Has the solution been automatically tested - are automated tests written?)
  • Peer-reviewed (Has the solution been reviewed and approved by the team/peers?)
  • Manually tested (Has the solution been tested manually by the appropriate people/teams - ED, QA, etc.?)
  • Documented (Has the documentation been prepared - public, internal, dev, etc.?)
  • Delivered (Has the solution been delivered (is available) to the relevant people/teams/stockholders?)
  • Announced (Has the solution been announced internally? Do the people in the team/company know about this solution/task/feature?)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant