Software tester

Application Under Test (AUT)

AUT is "Application under test". Once the development team is done with the coding part of Software Development Life Cycle(SDLC), then the build is progressed to Testing for validating and verifying its functionalities against the requirements. This coded application under testing is called Application Under Test (AUT).

Agile

Agile methodology is a project management framework that breaks projects down into several dynamic phases, commonly known as sprints.

agile

Agile methodology is a project management framework that breaks projects down into several sprints aka dynamic phases

Artifacts

An artifact is a byproduct of software development that helps describe the architecture, design and function of software. Artifacts are like roadmaps that software developers can use to trace the entire software development process. Artifacts might be databases, data models, printed documents or scripts.

software defect

Any error that, that could cause a software system to fail

Functional Testing

Concentrates on can user freely navigate the screens without issues, checks if error messages are displayed. checks the functionalities of the software testing.

DevOps

DevOps is a collaboration between Development and IT Operations to make software production and Deployment in an automated & repeatable way. DevOps helps increase the organization's speed to deliver software applications and services.

Test Strategy

Document that describes the way testing will be carried out. It answers qs like what you want to get done and how you are going to do it. It is created using the info from the business requirements. It outlines the testing objectives.

GitHub

GitHub is an online software development platform. It's used for storing, tracking, and collaborating on software projects. It makes it easy for developers to share code files and collaborate with fellow developers on open-source projects.

End-to-end testing

Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

Positive Testing

Testing aimed at showing software works using correct data.. Also known as "test to pass"

Adhoc testing

Testing carried out informally; no formal test preparation takes place, no recognized test design technique is used, there are no expectations for results. Objective is to find defects and break the application by executing any flow of application.

Black box testing

Testing the functionalities of software applications without having knowledge of internal code structure, implementation details and internal paths.

Sanity Testing

Performed after change in code to ensure that bugs have been fixed and no other issues have risen. Usually 15 minutes long.

Negative Testing

Performed using incorrect data. It validates if the system throws an error of invalid input and behaves as expected

UAT tester

Role that serves as the final round of testing to ensure the software is ready for end users.

Daily Scrum

Short about 15 minutes discussion where the team coordinates their activities for the following day. Not meant to report challenges or solve problems.

Repository

Storage location for software packages. AKA code repository. Managed by source control.

Graphical User Interface (GUI)

Type of user interface that allows a user to interact with software using text, graphics, and visual images, such as icons.

Scrum

Uses small teams to produce small pieces of deliverable software using sprints, to achieve an appointed goal

QA Lead

establishes metrics, mentors team members and manages outside resources, as well as developing test programs. ... Lead and mentor QA team members, as well as manage outside contract testers. Develop and execute test cases, scripts, plans and procedures (manual and automated).

Performance testing

evaluates how a system performs & responds under a particular workload. Performance tests are executed to examine speed, robustness, reliability, and application size.

business analysts role

gathers and collects info about the software the company will build

Smoke Testing

is a type of software testing that is typically performed at the beginning of the development process to ensure that the most critical functions of a software application are working correctly also known as "Build Verification Testing" or "Build Acceptance Testing,"

Program Manager role

manages multiple projects for specific products, teams, or programs and prepares the project

code freeze

period in time in which developers stop coding any changes to website

pipeline

set of processes that can be automated to compile and build and deploy code to production as efficiently as possible.

Cross Browser/Cross Device

testing being done or a bug is occurring on on multiple internet browsers or devices

UAT Testing (User Acceptance)

testing performed by the end user or the client to verify/accept the software system before moving the software application to the production environment

Maintenance/Regression

tests a software product against maintainability-how well it can be maintained.

Product Manager Responsibilities

they know everything about the product and how it works. The product life cycle, new product development, marketing program implementation.

QA TESTER/SOFTWARE TEST ENGINEER/QA ANALYST

they test the application by testing its functionality, performance, and security throughout the STLC

Exploratory Testing

type of software testing where test cases are not created in advance but testers check the system on the fly

Front end user testing

verify that a website or app's presentation layer is bug or error-free

Integration Testing also known as thread testing or string testing

verify that separate systems can work together passing data back and forth correctly

Backend Testing

when an input or data is entered on the front end application, it is stored in the database and the testing of such database is known as database testing or backend testing.

API (Application Programming Interface)

enables communication between applications using

Sprint Planning

A collaborative event in Scrum in which the Scrum team plans the work for the current sprint.

relational database

A database that represents data as a collection of tables in which all data relationships are represented by common values in related tables

test plan

A document that specifies how a program is to be tested

Scrum Master

A person who ensures that the team is productive, facilitates the daily Scrum, removes barriers that prevent the team from being effective- similar to a project manager. the Scrum Master is focused specifically on the team and ensuring they are effective and achieve the project goals.The Scrum Master is not focused on time, scope and budget, but rather building and supporting an environment where a team can iteratively and incrementally build products and improve their system,

Product Backlog

A prioritized list of user stories, showing both short- and long-term goals of a software development team.

Acceptance Criteria

A set of conditions that is required to be met before deliverables are accepted.

sprint

A set period of time normally two to four weeks, during which specific work must be completed and made ready for review when using Scrum methods

Sprint Backlog

A sprint backlog is a list of work items your team plans to complete during a project sprint.

API testing

In API Testing, instead of using standard user inputs(keyboard) and outputs, you use software to send calls to the API, get output, and note down the system's response. a software testing type that validates Application Programming Interfaces (APIs).

Burndown Chart

It is a graphic representation of the rate at which work is completed and how much work remains to be done. The Sprint Burndown Chart makes the work of the Team visible.

shift left

It's what you do before you test. >look at the user story 1st, look and see if it has the quality acceptance criteria, gather test data, create template for what the test case will be. Going to make sure I have what I need so i can understand what I'm testing and how I am going to to assess the functional aspects of a software application. To check whether you're getting the results your expecting. Examples: end to end, interface testing, smoke testing, acceptance testing I'm gonna test it. Then when its ready to test I'm going to create the step bu step and execute the case.

Happy Path Testing

It's what you do when you have limited documentation. In this case you would create test cases based around what the steps would look like it would take .

Software testing tools & Bug Defect managemnt

Jira, Zephyr, Testrail, Katalon Studio, Azure Devops, Appium, Bugzilla. Cucumber

Load Testing

Load testing is a kind of performance testing which determines a system's performance under real-life load conditions.

White Box Testing

Occurs when a tester is provided full details of a system including the source code, diagrams, and user credentials in order to conduct the test

what are the 6 phases of the SDLC?

Requirement Analysis Test Planning Test case development Test Environment setup Test Execution Test Cycle closure

Regression Testing

The process of testing changes to computer programs to make sure that the older programming still works with the new changes. Testing is done to ensure new code changes do not have side effects on existing functionalities. Test cases that are already executed are re-executed to ensure existing functionalities work fine.

QA Automation Engineer

This person automates the testing process using tools such as Katalon, Selenium or any automation tool.

deploy (v) or deployment (n)

To release product

Waterfall

Waterfall project management is a sequential project management methodology that's divided into distinct phases. Each phase begins only after the previous phase is completed.

showstopper

a bug that prevents you from any further testing

Requirement Traceability Matrix (RTM)

a document that maps and traces user requirements with test cases. It captures all the requirements proposed by the client and requirement traceability in a single doc., delivered at the end of the SDLC

Scenario Testing

an approach to release testing whereby you devise typical scenarios of use and use these scenarios to develop test cases for the system

Sprint retrospective

an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

test data

any data used during testing real data, fake/dummy data

Monkey Testing

carried out by a tester assuming if a monkey uses the application then how random input and values will be entered by the monkey without any knowledge or understanding of the application

Increment

collection of the backlog items that meet the teams definition of done