🃏
Hustling
Senior SDET | Test Automation Expert | 12+ Years in QA Leadership | WebdriverIO, Selenium, Cypress | 40%+ Test Coverage Improvement | API, Web, Mobile Expert
-
Airtable
- New York
- http://sajjad.nyc
- http://sajjadhossain.github.io
- in/sajjad-hossain-nyc
Pinned Loading
-
-
terra
terra PublicThe Vagrant shipping my GatsbyJS blog to a Nanode, built with CircleCI, and tested with Jest BDD.
Shell
-
Quality Approaches to Testing Software
Quality Approaches to Testing Software 1# QA Test Planning Methodology23## Planning4To begin the planning stage, QA's have to meet with developers and/or product owners and/or clients to discuss the documentation and project scope prior to implementation to begin the planning stage. Documentation comes in various forms, from paper to electronic, but no matter what kind, these product/project documents have to be analyzed. The time reading it should also be time dedicated to looking for any discrepancies and issues, meanwhile also building and spec'ing test dependancies, frameworks and cases. The product document is examined thoroughly for complexity, UI features, functionality, issues and most importantly `requirements`; some aspects may need to be changed to work. Analysis as a QA is feedback for the developers.
5 -
How to Reproduce a Bug
How to Reproduce a Bug 1# Reproducing Bugs2## How to File a Bug34When filing bugs, or jotting down [steps-to-reproduce](https://en.wikipedia.org/wiki/Software_bug), you should try to have the following information:
5
Something went wrong, please refresh the page to try again.
If the problem persists, check the GitHub status page or contact support.
If the problem persists, check the GitHub status page or contact support.

