Questions and answers

The job of the test person is to go through all parts of the software, through the interface or within the code lines, to check which parts are bugs and present them to the programmers.
The software checker has multiple thinking and responsibility types. Such as thinking about design, efficiency and inferior interface, etc.
The reviewer returns the findings to related people such as product manager and designers.
A software tester is called Quality control Quality assurance.

Quality Assurance:
A department that has the end to ensure the quality of the organization's functioning and products. Execution by work procedures and standards, management of its results, document control.

Software Test Report / Software Test Results - Software Test Report A document containing the documentation of the test execution and other important data such as: 1. Failure summary and severity 2. Statistical data on the test course.

Software Test Plan
Document that provides a framework for a software testing project:
* Review of the system under review - what is planned to test in terms of QC.
* Method and content of tests.
* Required resources for testing - Training of testers, testing tools.
* Test management and interface management with other teams. * Control point and reporting.
* Risk control.

Software Test Description - Test Specification Document. * Document specifying the planned test cases with reference to the expected input and output data. * Define prerequisites from the database and a detailed description of the test environment components.

Software Problem Report -
Document development bug details.
* Document detailing the list of faults discovered during the tests. * The report lists closed and open faults in different sections: project / development team / hardware / open / closed.

Unit testing - From Wikipedia, the free encyclopedia

Unit tests are software tests at the smallest system unit level (module) that verify the unit's proper operation.
Testing should take place after the initial writing of the module or after making specific changes.
The idea is to create a set of tests, which will cover all module activity, and its success will reasonably prove that the module is working properly. This type of testing is usually performed by developers and not by end users.

Integration testing - From Wikipedia, the free encyclopedia

Software integration testing is also called integration testing is one of the software tests designed to test the effect that a given part of a software has with other parts of it and with other software that it interfaces with, such as an operating system.
Integration testing is a phase during software testing where several individual modules are connected and connected to a system or subsystem, or to an external system.
The integration tests are usually performed after all unit tests have been performed.
Purpose The integration tests are to test the central functionality and performance of the system between the various items.

System tests-Wikipedia, the free encyclopedia
Testing the system as a whole, usually seeing the user of the system's capabilities.

Admission tests - From Wikipedia, the free encyclopedia

Admissions tests are a set of tests that a customer or user sets for a product, and is designed to ensure that the product meets all of its needs and requirements.
Acceptance checks are usually performed by the product orderer, after the product has been delivered to the ordering party by the producing body.
Admissions testing is an integral part of quality assurance processes, and in software products - software testing.

Functional testing - from Wikipedia, the free encyclopedia - to verify system activity.
These tests are based on the requirements document and the characterization screen and aim to check that the system does what it needs and does not do what it does (valid and invalid testing).

Useful tests - From Wikipedia, the free encyclopedia
Convenience testing and application design efficiency and accessibility for disabled people. For example: ease of use of menus, convenient navigation and site orientation.

Client interface testing - from Wikipedia, the free encyclopedia

Check the controls and fields on the screen. Good behavior, a format of fields, according to the legality defined at the screen level and not the business logic. For example: Checking minimum and maximum characters in the field.

Load testing - From Wikipedia, the free encyclopedia

Verify server side response capability in server / client systems that many users are expecting at the same time. These tests focus on measuring response times and finding the "breaking point" of the system. Apart from "virtual users", we also test loads resulting from transactions and jobs that occur "in the stomach" of the system (not just business processes).

Performance testing - From Wikipedia, the free encyclopedia
Product performance testing at various configurations and load levels, and performance measurement for documentation / comparison requirements.

Withdrawal tests-Wikipedia, the free encyclopedia
Validates the system activity after it has been modified. Verify that what worked has not been broken in the wake of the transfer of a version.

System Integration Tests - From Wikipedia, the free encyclopedia
To verify the ability to integrate the software / component into an existing / new system (for example - compatibility of the software with operating system updates, different browsers, other software that the software should work with, etc.).

Alpha / Cell Testing - From Wikipedia, the free encyclopedia
Tests performed by a defined user group are closed (alpha) or open (in cell) which use the product and report flooding errors while in regular use.

Insanity checks - from Wikipedia, the free encyclopedia
Basic testing that allows you to quickly and efficiently identify if the basic functionality of the product is working properly and the product is in stable condition.

Smoke Tests - From Wikipedia, the free encyclopedia
Another type of testing is designed to quickly identify the stability of the product, by early detection of malfunctions that indicate a serious failure of any component of the product. Unlike sanity tests, smoke tests are usually performed more intuitively and flexibly, and not necessarily according to predetermined scenarios.

בדיקות קופסה שחורה -מתוך ויקיפדיה, האנציקלופדיה החופשית
בדיקות קופסה שחורה (באנגלית Blackbox testing) על פי ארגון ה-ISTQB הן 'בדיקות פונקציונאליות או לא פונקציונאליות המתבצעות ללא התייחסות למבנה הפנימי של הרכיב או המערכת'. זוהי שיטה להגדרת בדיקות ולא שלב במעגל החיים של המוצר. לפיכך ניתן לבצע בדיקות קופסה שחורה בכל אחת מהרמות של בדיקות התוכנה: בדיקות יחידה, בדיקות אינטגרציה, בדיקות מערכת ובדיקות קבלה.
בבדיקות קופסה שחורה מתייחסים אך ורק לקלט ולפלט שהבודק מכניס לתוך המערכת, והבדיקה היא שהפלט המתקבל או הפעולה שקרתה באמת זהה לצפי. בשל כך, רוב הבדיקות הנערכות במסגרת בדיקות אלו הן פונקציונאליות שכן בדיקות לא פונקציונאליות קשה יותר לבדוק במידה ואין יכולת לשנות את מצבה הפנימי של המערכת.
המשלים לבדיקות קופסה שחורה הן בדיקות קופסה לבנה, שהיא שיטה לבדיקת ההשפעה שיש לקלט או לפלט על המבנה הפנימי של המערכת.

Edit White Box tests. Focuses on the inner structure of the program: trajectories and calculations that correspond to different input states.