Software Testing

1.  Bug
- When actual result deviates from the expected result while testing a software application or product then it results into a defect. Hence, any deviation from the specification mentioned in the product functional specification document is a defect. In different organizations it’s called a Bug. 

2. Defect
- If software misses some feature or function from what is there in requirement it is called as defect. 


3. The Capability Maturity Model for Software (CMM or SW-CMM) 
- is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes.


4. Beta testing 
- is testing of a release of a software product conducted by customers.

5. Black Box Testing
-Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component.

6. Bottom Up Testing
-An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.

7. Boundry Testing
-Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).

8. Boundry Value Analysis (BVA)
- is similar to Equivalence Partitioning but focuses on "corner cases" or values that are usually out of range as defined by the specification. This means that if a function expects all values in range of negative 100 to positive 1000, test inputs would include negative 101 and positive 1001.
9. Branch Testing
- Testing of all branches in the program source code is called Branch Testing.

10. Coding
- The generation of source code is called Coding.

11. Compatibility Testing
- Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware.
12. Component
- A component is an identifiable part of a larger program or construction. Usually, a component provides a particular function or group of related functions.
13. Component Testing
- Testing of individual software components is called Component testing.

14. Acceptance Testing
- Testing conducted to enable a user/customer to determine whether to accept a software product. - Normally performed to validate the software meets a set of agreed acceptance criteria.

15. Accessibility Testing
-Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).

16. Ad Hoc Testing
- A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality is called Ad Hoc testing. This can include negative testing also.
17. Agile Testing
- Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm. See also Test Driven Development.
18. Application Binary Interface (ABI)
- A specification defining requirements for portability of applications in binary forms across different system platforms and environments is called Application Binary Interface (ABI).
19. Application Programming Interface (API)
- A formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services is called Application Programming Interface (API).
20. Automated Software Quality (ASQ)
- The use of software tools, such as automated testing tools, to improve software quality is called Automated Software Quality (ASQ).
21. Automated Testing
- Testing employing software tools which execute tests without manual intervention is called Automated Testing. Can be applied in GUI, performance, API, etc. testing. The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.
22. Backus-Naur Form
- It is a meta-language used to formally describe the syntax of a language.
23. Basic Block
- A sequence of one or more consecutive, executable statements containing no branches is called Basic Block.
24. Basis Path Testing
- A white box test case design technique that uses the algorithmic flow of the program to design tests.
25. Basis Set
-The set of tests derived using basis path testing.
26. Baseline
- The point at which some deliverable produced during the software engineering process is put under formal change control.

27. Binary Portability Testing
- Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification is called Binary Portability Testing.
28. Breadth Testing
- A test suite that exercises the full functionality of a product but does not test features in detail is called Breadth Testing.
29. Computer Aided Software Testing (CAST)
- Computer Aided Software Testing refers to the computing-based processes, techniques and tools for testing software applications or programs.
30. Capture/Replay Tool
- A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time. Most commonly applied to GUI test tools.

32. Cause Effect Graph
- A graphical representation of inputs and the associated outputs effects which can be used to design test cases.

33. Code Complete
- Phase of development where functionality is implemented entirety; bug fixes are all that are left. All functions found in the Functional Specifications have been implemented.

34.Code Coverage
- An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.

35. Code Inspection
- A formal testing technique where the programmer reviews source code with a group who ask questions analyzing the program logic, analyzing the code with respect to a checklist of historically common programming errors, and analyzing its compliance with coding standards. Know more about the Inspection in software testing.

36. Code Walkthrough
- A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer's logic and assumptions. Know more about Walkthrough in software testing. 

////////////////

"Autmoating chaos just gives faster chaos" Dororthy Graham

Failing to plan is plan to fzail

80% application 
20% usage

Zasada Pareta 80/20

-Smoke test
-simple failures
-crucial functions

Test Design
-Security
-Performance
-Usability
-Compatibility
-Funcionality

Test-Design Teschniques:
-Funcional Analysis (expected behaviour from funcional specifications)
-Equivalence Partitioning (initial conditions that produce similar results)
-Path Analysis (connections and stnctnce)
-Baundry Value ( input edit logic, filtreting out invalid data works correctly)
-Orthogoral Arrays


Test Procedure Template (ensure)
-Consistency
-Completeness
-Repeatability

Explotory testing
-How softawre works -> row to handle different cases

1. Review design and requirements
2. Planning the test
3. Designing the test
4. Setting up the test Env.
5. Carrying out the test
6. Final Reporting