Develop

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report 🐞
+about: Create a report to help us improve
+title: "[BUG]"
+labels: bug
+assignees: ''
+
+---
+
+### Describe the bug
+A clear and concise description of what the bug is.
+
+### To Reproduce
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+### Expected behavior
+A clear and concise description of what you expected to happen.
+
+### Screenshots
+If applicable, add screenshots to help explain your problem.
+
+### Desktop (please complete the following information):
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+### Smartphone (please complete the following information):
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+### Additional context
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,19 @@
+---
+name: Feature request 💡
+about: Suggest an idea for this project
+title: "[FEATURE REQUEST]"
+labels: enhancement
+assignees: ''
+
+---
+### Is your feature request related to a problem? Please describe.
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+### Describe the solution you'd like
+A clear and concise description of what you want to happen.
+
+### Describe alternatives you've considered
+A clear and concise description of any alternative solutions or features you've considered.
+
+### Additional context
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,21 @@
+**What does this PR do?**
+
+Fixes #issue_number (replace issue_number with the issue number this PR solves)
+
+Summarise the main tasks handled in the pull request
+
+**description of Task to be completed?**
+
+Describe (in detail) what the task completed in the pull request does as per the relevant task
+
+**How should this be manually tested?**
+
+Give bullet point instructions on how to setup the code and test it manually (Assume no prior experience on JS or code)
+
+**Any background context you want to provide?**
+
+Any pertinent information that should be considered
+
+**Questions:**
+
+If something is unclear or you want some questions to be addressed by your peers, mention them here

.github/workflows/ci.yml

@@ -0,0 +1,32 @@
+# This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node
+# For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions
+
+name: Node.js CI
+
+on:
+  push:
+    branches:
+      - develop
+  pull_request:
+    branches:
+      - develop
+      - master
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [10.x, 12.x, 14.x]
+
+    steps:
+    - uses: actions/checkout@v2
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v1
+      with:
+        node-version: ${{ matrix.node-version }}
+    - run: npm ci
+    - run: npm test
+    - run: npm run test:e2e

.github/workflows/github-pages.yml

@@ -0,0 +1,24 @@
+name: GitHub Pages
+
+on:
+  push:
+    branches:
+      - master
+
+jobs:
+  deploy:
+    runs-on: ubuntu-18.04
+    steps:
+      - uses: actions/checkout@v2
+
+      - name: Install and Build 🔧 
+        run: |
+          npm install
+          npm run build
+
+      - name: Deploy 🚀
+        uses: JamesIves/[email protected]
+        with:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          BRANCH: gh-pages # The branch the action should deploy to.
+          FOLDER: build # The folder the action should deploy.

README.md

@@ -1 +1,5 @@
 # Comments Microservice Dashboard
+
+![GitHub Pages](https://github.com/microapidev/comment-microapi-admin-dashboard/workflows/GitHub%20Pages/badge.svg?branch=master) ![Node.js CI](https://github.com/microapidev/comment-microapi-admin-dashboard/workflows/Node.js%20CI/badge.svg?branch=master) ![license: MIT](https://img.shields.io/github/license/microapidev/comment-microapi-admin-dashboard)
+
+> [Live Page](https://microapidev.github.io/comment-microapi-admin-dashboard)

cypress.json

@@ -0,0 +1,8 @@
+{
+  "baseUrl": "http://localhost:3000",
+  "integrationFolder": "cypress/integration",
+  "screenshotsFolder": "cypress/screenshots",
+  "supportFile": false,
+  "pluginsFile": false,
+  "video": false
+}

cypress/fixtures/example.json

@@ -0,0 +1,5 @@
+{
+  "name": "Using fixtures to represent data",
+  "email": "[email protected]",
+  "body": "Fixtures are a great way to mock data for responses to routes"
+}

cypress/integration/login/login.e2e.js

@@ -0,0 +1,40 @@
+/// <reference types="cypress" />
+
+describe("Login Page", () => {
+  beforeEach(() => {
+    cy.visit("/");
+  });
+
+  describe("Queries", () => {
+    it("should redirect to the login page", () => {
+      cy.url().should("include", "#/login");
+    });
+
+    it("should focus on username input", () => {
+      cy.get("#username").should("be.focused");
+    });
+
+    it("should require username and password", () => {
+      cy.get("#username-helper-text").should("not.exist");
+      cy.get("#password-helper-text").should("not.exist");
+      cy.get("#username").blur();
+      cy.get("button[type=submit]").click();
+      cy.get("#username-helper-text").should("contain.text", "Required");
+      cy.get("#password-helper-text").should("contain.text", "Required");
+    });
+  });
+
+  describe("Actions", () => {
+    it("should have the inputted username value", () => {
+      cy.get("#username")
+        .type("[email protected]")
+        .should("have.value", "[email protected]");
+    });
+
+    it("should have the inputted password value", () => {
+      cy.get("#password")
+        .type("fakepassword")
+        .should("have.value", "fakepassword");
+    });
+  });
+});

cypress/plugins/index.js

@@ -0,0 +1,19 @@
+/// <reference types="cypress" />
+
+// This function is called when a project is opened or re-opened (e.g. due to
+// the project's config changing)
+
+/**
+ * @type {Cypress.PluginConfig}
+ */
+module.exports = (on, config) => {
+  // `on` is used to hook into various events Cypress emits
+  // `config` is the resolved Cypress config
+
+  // custom tasks for sending and reporting code coverage
+  require("@cypress/code-coverage/task")(on, config);
+
+  // It's IMPORTANT to return the config object
+  // with any changed environment variables
+  return config;
+};

cypress/support/commands.js

@@ -0,0 +1,25 @@
+// ***********************************************
+// This example commands.js shows you how to
+// create various custom commands and overwrite
+// existing commands.
+//
+// For more comprehensive examples of custom
+// commands please read more here:
+// https://on.cypress.io/custom-commands
+// ***********************************************
+//
+//
+// -- This is a parent command --
+// Cypress.Commands.add("login", (email, password) => { ... })
+//
+//
+// -- This is a child command --
+// Cypress.Commands.add("drag", { prevSubject: 'element'}, (subject, options) => { ... })
+//
+//
+// -- This is a dual command --
+// Cypress.Commands.add("dismiss", { prevSubject: 'optional'}, (subject, options) => { ... })
+//
+//
+// -- This will overwrite an existing command --
+// Cypress.Commands.overwrite("visit", (originalFn, url, options) => { ... })

cypress/support/index.js

@@ -0,0 +1,22 @@
+// ***********************************************************
+// This example support/index.js is processed and
+// loaded automatically before your test files.
+//
+// This is a great place to put global configuration and
+// behavior that modifies Cypress.
+//
+// You can change the location of this file or turn off
+// automatically serving support files with the
+// 'supportFile' configuration option.
+//
+// You can read more here:
+// https://on.cypress.io/configuration
+// ***********************************************************
+
+import "@cypress/code-coverage/support";
+
+// Import commands.js using ES2015 syntax:
+import "./commands";
+
+// Alternatively you can use CommonJS syntax:
+// require('./commands')