Book Image

Vue.js 2 Design Patterns and Best Practices

By : Paul Halliday
Book Image

Vue.js 2 Design Patterns and Best Practices

By: Paul Halliday

Overview of this book

Vue.js 2 Design Patterns and Best Practices starts by comparing Vue.js with other frameworks and setting up the development environment for your application, and gradually moves on to writing and styling clean, maintainable, and reusable Vue.js components that can be used across your application. Further on, you'll look at common UI patterns, Vue form submission, and various modifiers such as lazy binding, number typecasting, and string trimming to create better UIs. You will also explore best practices for integrating HTTP into Vue.js applications to create an application with dynamic data. Routing is a vitally important part of any SPA, so you will focus on the vue-router and explore routing a user between multiple pages. Next, you'll also explore state management with Vuex, write testable code for your application, and create performant, server-side rendered applications with Nuxt. Toward the end, we'll look at common antipatterns to avoid, saving you from a lot of trial and error and development headaches. By the end of this book, you'll be on your way to becoming an expert Vue developer who can leverage design patterns to efficiently architect the design of your application and write clean and maintainable code.
Table of Contents (19 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Free Chapter
1
Vue.js Principles and Comparisons
12
Server-Side Rendering with Nuxt
Index

Unit testing


Automated testing tools take the manual work we'd be doing each time we want to verify that our feature works as expected, and give us a way to run a command that tests our assertions one by one. This is then shown to us in reports (or live in our editor, as we'll see later on), which gives us the ability to refactor code that isn't working as intended.

By using automated testing tools, we're saving ourselves a vast amount of effort when compared to manual testing.

Unit testing can be defined as a type of testing that only tests one "unit" (the smallest testable part of a feature) at a time. We can then automate this process to continually test our features as the application gets larger. At this point, you may wish to follow Test-Driven Development/Behavior Driven-Development practices.

In the modern JavaScript testing ecosystem, there are a variety of test suites available. These test suites can be thought of as applications that give us the ability to write assertions, run our...