Skip to content

Write a How we Test entry in the Contributing Guidelines #30

Description

@mdb1

Add different sections outlining how to test different layers:

  • VMs
  • Repositories
  • Services
  • NotificationCenter
  • etc

Add a bottom-line phrase to serve as a rule of thumb to whether a test is useful or not. Something in the lines of:
"We want a test to fail if a functionality line is accidentally commented/removed"

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions