Frontend

Languages/Libraries

HTML5

CSS3

Vanilla JavaScript(ES5 and beyond) - We follow Google JavaScript Style guide

ReactJS

SEO and google analytics

Editors

Visual Studio Code Editor

Atom

Sublime

Whatever you can create magic with>

Git Workflow - We follow best git practices

Master branch for production releases

acceptance branch for acceptance

Develop branch for development and staging

CI/CD setup by DevOps

Checkout develop for every new branch

Branch permissions setup - no merging directly to develop, acceptance and master

Commit messages standard - We do follow Angular commit messages style.

Always use a PR template working in a team for code reviews

TDD - Test Driven Development

code without tests is broken by design Jacob Kaplan

React Testing Library

Jest

Enzynme

Sinon

Accessiblity

Ease of use | obtain | understanding | reached

Navigable - Media access, distinguishable, adaptable to different environments

Operable - keyboard & mouse accessible, quality time

understandable - content is readable, predictable, allows input assistance.

Robust

README.md - Code documentation

System requirements e.g. NodeJS version x

Technologies, libraries and dependencies used

Getting started

Where to get the secret variables

Project Setup

Bitbucket Repo

CI/CD setup

Design mockup access

Used CRA - Create-react-app, Gatsby template or setup from scratch considering the teams folder structure

Setup linting rules

Setup hooks e.g. pre-commit, pre-push

Project Management

Backend

Languages/Libraries

Java - Spring

Python - Django

PHP - Laravel

SQL

Editors

Intelli J

Whatever you can create magic with

Git Workflow - We follow best git practices

A good is someone who always look both ways before crossing a one way street

Master branch for production releases

acceptance branch for acceptance

Develop branch for development and staging

CI/CD setup by DevOps

Checkout develop for every new branch

Branch permissions setup - no merging directly to develop, acceptance and master

Commit messages standard - We do follow Angular commit messages style.

Always use a PR template working in a team for code reviews

README.md - Code documentation

System requirements e.g. NodeJS version x

Technologies, libraries and dependencies used

Getting started

Where to get the secret variables

Project Setup

Bitbucket Repo

CI/CD setup

Design mockup access

Used CRA - Create-react-app, Gatsby template or setup from scratch considering the teams folder structure

Setup linting rules

Setup hooks e.g. pre-commit, pre-push

QA - Quality Assuarance

QA Process

• Developer create a feature branch and commit changes
• Create a PR to execute unit test/integration scripts
• Code review (SonarQube / manual)
• Merge feature branch to develop
• Execute API script (Rest Assured) or postman
• Execute functional UI script (BDD/TDD) Automate: cucumber/selenium, Junit/TestNG, Maven/Gradle
• Execute accessibility script (Automate: Cypress axe (node js / vs code))
• Perform and End-to-End testing (manual(optional))
• Promote to staging
• Execute performance script (Automated: Gatling (Scala) or Jmeter (Java))
• Promote to Gold then Deploy (Permissions required)

Tools

• Jira
• Browserstack - Applive/ live (Manual web and mobile app testing)
• Testrail - Manual Test management (test cases, runs and results)
• Jenkins - CI tool (Circle CI) - GCP

QA Security

• Permissions on the release management/bitbucket ( Role)
• Manage documents on confluence (manage project documents)

DevOps

Bitbucket Project Setup

Bitbucket Repo

CI/CD setup

GCP Security

Bitbucket branch access to specific developers

Store project passwords safe