Frontend
1.0.0
1.0.0
  • Introduction
  • Project Guidelines
    • INTRODUCTION
    • PROJECT SETUP
      • Frameworks
      • Static type checking
      • Code Quality Tools
      • Enforcing good practices
      • Testing
      • Code versioning flow
      • Continuous Integration & Delivery
      • Isolated component development
    • EFFECTIVE AND CONSISTENT WORKFLOW
      • Code structure, architecture
      • Code versioning and review flow
      • Testing
      • Continuous Integration & Delivery
      • Dependency checking
      • Project Management Tools
      • Communication
    • THE QUALITY OUTPUT
      • Great UX/UI
        • Design & User Experience
        • SEO, SMO
      • Accessibility
        • Introduction
        • Why a11y?
        • Fundamentals
        • A11y in STRV
          • Share Knowledge
          • Project Life Cycle
          • A11y culture
      • Performance
        • Bundle Size
        • Deployment
        • Audits & Reports
      • Stability
        • Documentation
        • Analytics & Error Tracking
        • Quality Assurance
      • Security
    • FINAL WORDS
    • ACKNOWLEDGEMENT
Powered by GitBook
On this page

Was this helpful?

  1. Project Guidelines
  2. EFFECTIVE AND CONSISTENT WORKFLOW

Testing

PreviousCode versioning and review flowNextContinuous Integration & Delivery

Last updated 5 years ago

Was this helpful?

was already described in the Project Setup chapter. If you want to make your workflow effective and consistent, you should definitely start writing tests.

It’s a very useful investment which, besides guarding your code quality and helping you ship new versions without bugs, also helps you during the refactoring.

It’s crucial to have tests, especially when you are coming back to the project after some time. It happens that you just don’t remember some things. And tests could serve as documentation.

Usually, the absence of meaningful tests makes it almost impossible to take over somebody else’s codebase. If you do so, you will have bad velocity on a project. And you won’t be sure if you’re risking breaking something by making a change in the code.

The importance of tests