You're reading from Architecting Vue.js 3 Enterprise-Ready Web Applications Build and deliver scalable and high-performance, enterprise-ready applications with Vue and JavaScript

Product type Paperback

Published in Apr 2023

Publisher Packt

ISBN-13 9781801073905

Length 272 pages

Edition 1st Edition

Languages

JavaScript

Tools

Vue

Concepts

Front End Web Development

Author (1):

Solomon Eseme

View More author details

Table of Contents (21) Chapters

Preface

1. Part 1: Getting Started with Vue.js

2. Chapter 1: Getting Started with Vue.js 3 FREE CHAPTER

3. Chapter 2: Using Libraries for Large-Scale Applications

4. Part 2: Large-Scale Apps and Scaling Performance in Vue.js 3

5. Chapter 3: Scaling Performance in Vue.js 3

6. Chapter 4: Architecture for Large-Scale Web Apps

7. Chapter 5: An Introduction to GraphQL, Queries, Mutations, and RESTful APIs

8. Chapter 6: Building a Complete Pinterest Clone with GraphQL

9. Part 3: Vue.js 3 Enterprise Tools

10. Chapter 7: Dockerizing a Vue 3 App

11. Part 4: Testing Enterprise Vue.js 3 Apps

12. Chapter 8: Testing and What to Test in Vue.js 3

13. Chapter 9: Best Practices in Unit Testing

14. Chapter 10: Integration Testing in Vue.js 3

15. Chapter 11: Industry-Standard End-to-End Testing

16. Part 5: Deploying Enterprise-ready Vue.js 3

17. Chapter 12: Deploying Enterprise-Ready Vue.js 3

18. Chapter 13: Advanced Vue.js Frameworks

19. Index

Why subscribe?

20. Other Books You May Enjoy

What to test

A popular question among software teams is what should we test and what should we not test? In this section, we will explore the different things you should and shouldn’t test when considering software tests.

We will first explore different test strategies to employ when integrating software testing into your development workflow.

Testing strategy

The best testing strategy to implement in your enterprise application is the combination of normal (manual) testing and automated testing. In addition, normal testing should be done more extensively by the Quality Assurance (QA) team.

To explain this further, when automated testing is written and implemented successfully, we usually program it to look for fundamental errors and edge cases that may not properly assimilate how a real customer will interact with the application.