There are advantages and disadvantages of monorepos and many who use them have their own reason for why it works best for them. When I first started looking into monorepos I found my self wondering, what kind of technologies are used to manage vast quantities of code and collaboration? To answer this question Ill go over some of these technologies, what they are, and how they work for monorepos.
There’s a lot of things that can be done with various CI/CD tools but, in the scope of testing we really only need to focus on test automation. Since we’ll be using GitHub to host this project we can utilize GitHub Actions to automate our tests. GitHub Actions allow developers to automate the development life cycle.
A cache is a storage method for subsets of data that can be read at high speeds so that future requests for data can be received much faster. We see and use cached data everyday, It’s one of the reasons our favorite websites can deliver content as quickly as it does. When a request is made to Facebook.com for example, much of the static data, or data that doesn’t change often, is loaded quickly from cache while other data is retrieved from a server.
To understand more about TypeScript lets first understand what it is, a static type checker. Type checking is the process of checking the data types to insure there are no type errors and that code will behave with the type of data you would expect. Some languages can be pretty relaxed when it comes to changing or manipulating data types, for example in JavaScript you can do operations like:
When I first started looking into Next.js and how they recommend developers test an application using it, I found very little information. Their website has no documentation on it and their GitHub readme doesn’t have any opinions on it either. If we take a look at other frameworks, Vue.js has a guided section on unit, integration, and end-to-end testing. Angular also has a setup guide with example configurations.