Skip to content

SomthingInteresting/study-buddy

Repository files navigation

Bank_Tech_Test README

Table of Contents

1. Specifications
2. Observations
3. User Story
4. Diagram
5. Methodology Implementaion
6. Tickets
7. Test Covarage
8. Screenshots: program tested in terminal
9. Instructions

Technologies

Technologies Here's an overview of the technologies used to build this template application. You don't need to do a deep dive on each one right now. Instead, try to get a feeling for the big picture and then dive into the details when a specific task pushes you in that direction.

M is for MongoDB MongoDB is a NoSQL database program that stores data in collections of documents (in a format similar to JSON), rather than in tables. The application interacts with MongoDB using a tool called Mongoose.

E is for Express Express is the Javascript equivalent of Sinatra. The structure of this application will feel quite different to what you're used to but the principles are the same.

R is for React React is a hugely popular tool that is used to build engaging front ends. The basic principle is that the front end is split up into components, each of which could include some logic, template structure (HTML) and styling (CSS).

N is for Node Java script was originally designed to run exclusively in browsers, such as Chrome. Node is a tool that allows you to run Javascript outside the browser and its invention made it possible to build full stack Javascript apps.

We also used...

Jest for unit testing on the back end Cypress for end-to-end testing and component testing, on the front end Mongoose to model objects in MongoDB. Handlebars for the home template. ESLint for linting. Nodemon to reload the server automatically. Architecture This application is comprised of two distinct pieces.

A backend API built with Express A front end built with React The React front end sends HTTP requests to the backend API and receives JSON in response body, rather than a whole page of HTML.

1. Specifications

Requirements

  • TEXT

2. Observations

3. User Story


4. Diagram

1. Diagram Version 1 Text in case picture does not display

2. Diagram Version 2 Text in case picture does not display 2

5. Methodology Implementation

Research

This is how you add a link: test to link.

Controller functionality

  1. User Controller:
  • All about the user controller
  1. Example Controller:
  1. Example Controller:

Testing

  1. User Controller Tests:
  • key notes:

  • test (PASSED):

    • test
  1. Transaction Controller Tests:
  • key notes:
    • test
  1. Statement Controller Tests:
  • print

6. Tickets

7. Test Covarage

1. Test coverage:

1. Screenshot 1 Text in case picture does not display

2. Screenshot 2 Text in case picture does not display 2

4. ESlint - all errors fixed and cleared:

Note: in two situations this was used to call upon a method (see here for more details) and ESlint gave an error. One was fixed by turning the method into const declaration and the other by using the keyword staticand turned the (regurlar) method into a static method (read more here on static methods).

1. Screenshot 1 Text in case picture does not display

8. Screenshots: program tested in terminal

1. Screenshot 1 Text in case picture does not display

10. Finished product:

Text in case picture does not display

9. Instructions

Running JavaScript

Introduction

This program uses Javascript, a dynamic computer programming language and one of the core technologies for developing web page content, alongside HTML and CSS.

For this exercise to be run, a program called Node.js will have to be installed. Node.js is a JavaScript runtime, i.e. it reads JavaScript code and executes it as a programs

Step 1: Clone this repo to your machine:

# Create a folder/directory where you would like to store the cloned repo: 
$ mkdir cloned-repo

# Then switch to the newly created directory:
$ cd cloned-repo

# Inside the new fodler clone the repo, command which will copy all the existing files from the Git repository:
$ git clone link-to-git-repository

Step 2: Install nvm

Nvm stands for Node Version Manager, a tool that allows you to install and swtich in between different versions of Node. NVM is distributed using github - you can find installation instructions for the latest version here.

# You'll need to run a command that looks like this:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash

# Once that step is complete, reload your ~/.zshrc file:
source ~/.zshrc

# Now you can install Node by running: 
$ nvm install node

Step 3: Setting up the project

# When NVM is installed, once can automatically install and use the latest, stable version. You can set up the enviroment by running: 
$ nvm use node

#The next step would be to set up the folder structure, however this is not required as this has been already done. 

# Initialize NPM project, i.e. create the package.json file: 
$ npm init -y

# Add the jest package to run tests in the tests directory:
$ npm add jest

Step 4: Running tests:

# Please check that all tests are running in the test directory before running the program in REPL: 
$ npx jest

# alternatively try:
$ jest


# To see test coverage then run: 
$ npx jest --coverage

# alternatively try:
$ test

Step 5: Running the program:

OPTIONN 1



How was this resource?
😫 😕 😐 🙂 😀
Click an emoji to tell us.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published