Lesson 5 Flashcards
BRD
Business requirements document
Business requirement document (BRD)
A Business requirements document (PRD) focuses on the business perspective as it holds the details of the business solution for a project. Business requirements document also emphasizes the needs and expectations of the customer. In simpler terms, BRD indicates what the business wants to achieve. The BRD indicates all the project deliverables and the inputs and outputs associated with each process function. BRD focuses on the business objectives and distinguishes between the business solution and technical solution.
PRD
Product requirements document (PRD)
Product requirements document
A product requirements document (PRD) is a document containing all the requirements to a certain product. It is written to allow people to understand what a product should do.
Typically, a PRD is created from a user’s point-of-view by a user/client or a company’s marketing department. The requirements are then analyzed by a (potential) maker/supplier from a more technical point of view, broken down, and detailed in a Functional Specification (sometimes also called Technical Requirements Document).
TRD
Technical requirements document (TRD)
Technical requirements document
A Technical requirements document (TRD) is the document on the basis of which the development team implements the project, and which describes a list of functions and algorithms, interface requirements, system architecture requirements, development methodology, technological stack (what technologies will be used and why), and many other things.
Technical requirement specification contains comprehensive knowledge about the purpose of the system, functionality, and implementation methods.
What is Confluence?
A Confluence is a documentation platform that stores and organizes all of the information assets around the projects you’re doing in JIRA (like, product requirements), or general things like meeting minutes, marketing assets, design documents, how-to’s, etc.
Confluence and Jira were designed to complement each other, and have a number of integration points built-in, giving Confluence users the ability to view, interact with, and reference Jira issues from a Confluence page. QA may use confluence to view documentation and monitor release notes.
Test Plan
Test Plan outlines the common strategy that will be applied to test an application.
See materials for the example. Just take a quick look as you will never need to prepare such a document, it’s for managers and leads.
Test Case
Test Case is a series of minimal simple steps that have to be done to check a particular functionality.
Test Matrix
Test Matrix or Requirements Traceability Matrix (RTM) is a document that connects requirements throughout the validation process. The traceability matrix is a tool both for the validation team, to ensure that requirements are not lost during the validation project, and for auditors, to review the validation documentation.
See materials for the example. Just take a quick look as you will never need to prepare such a document.
TestRail
TestRail helps you manage and track your software testing efforts and organize your QA department. It makes it easy to create test cases, manage test runs and coordinate your entire testing process.
TestRail is used by thousands of teams, both small and large.
How to record a screen on PC & Mobile?
Often it’s necessary to record your screen and attach it to the ticket in Jira.
With QuickTime on Mac (you can also install QT on PC): video.
Ways to record your screen on Windows, macOS: a guide.
Android: guide.
iOS: guide.
- The easiest is probably to install QuickTime or SnagIt
