Book Image

Vue.js 2 and Bootstrap 4 Web Development

Book Image

Vue.js 2 and Bootstrap 4 Web Development

Overview of this book

In this book, we will build a full stack web application right from scratch up to its deployment. We will start by building a small introduction application and then proceed to the creation of a fully functional, dynamic responsive web application called ProFitOro. In this application, we will build a Pomodoro timer combined with office workouts. Besides the Pomodoro timer and ProFitOro workouts will enable authentication and collaborative content management. We will explore topics such as Vue reactive data binding, reusable components, routing, and Vuex store along with its state, actions, mutations, and getters. We will create Vue applications using both webpack and Nuxt.js templates while exploring cool hot Nuxt.js features such as code splitting and server-side rendering. We will use Jest to test this application, and we will even revive some trigonometry from our secondary school! While developing the app, you will go through the new grid system of Bootstrap 4 along with Vue.js’ directives. We will connect Vuex store to the Firebase real-time database, data storage, and authentication APIs and use this data later inside the application’s reactive components. Finally, we will quickly deploy our application using the Firebase hosting mechanism.
Table of Contents (19 chapters)
Vue.js 2 and Bootstrap 4 Web Development
About the Author
About the Reviewer
Customer Feedback

Testing Vuex store with Jest

Let's now try to test our Vuex store. The most critical parts of our store to test are our actions and mutations because they can actually mutate the store's state. Let's start with the mutations. Create the mutations.spec.js file in the test folder and import mutations.js:

// test/mutations.spec.js
import mutations from '~/store/mutations'

We are ready to write unit tests for our mutation functions.

Testing mutations

Mutations are very simple functions that receive a state object and set some of its attribute to the given value. Thus, testing mutations is fairly easy—we have just to mock the state object and pass it to the mutation we want to test with a value we want to set. In the end, we have to check whether the value has been actually set. Let's, for example, test the mutation setWorkingPomodoro. This is what our mutation looks like:

// store/mutations.js
setWorkingPomodoro (state, workingPomodoro) {
  state.config.workingPomodoro = workingPomodoro

In our test...