fbpx

SOFTWARE TESTING TERMS – III

วิธีการรับมือกับการเปลี่ยนแปลงในการงาน และ ชีวิต

24 Apr SOFTWARE TESTING TERMS – III

Posted at 09:08h in Software Testing, Software Testing Terminology, Technology News by
0 Likes

41. Endurance Testing: Type of testing which checks for memory leaks or other problems that may occur with prolonged execution. It is usually performed by performance engineers.

42. Exploratory Testing: Black box testing technique performed without planning and documentation. It is usually performed by manual testers.

43. Equivalence Partitioning Testing: Software testing technique that divides the input data of a software unit into partitions of data from which test cases can be derived. it is usually performed by the QA teams.

44. Fault injection Testing: Element of a comprehensive test strategy that enables the tester to concentrate on the manner in which the application under test is able to handle exceptions. It is performed by QA teams.

45. Formal verification Testing: The act of proving or disproving the correctness of intended algorithms underlying a system with respect to a certain formal specification or property, using formal methods of mathematics. It is usually performed by QA teams.

46. Functional Testing: Type of black box testing that bases its test cases on the specifications of the software component under test. It is performed by testing teams.

47. Fuzz Testing: Software testing technique that provides invalid, unexpected, or random data to the inputs of a program – a special area of mutation testing. Fuzz testing is performed by testing teams.

48. Gorilla Testing: Software testing technique which focuses on heavily testing of one particular module. It is performed by quality assurance teams, usually when running full testing.

49. Gray Box Testing: A combination of Black Box and White Box testing methodologies: testing a piece of software against its specification but using some knowledge of its internal workings. It can be performed by either development or testing teams.

50. Glass box Testing: Similar to white box testing, based on knowledge of the internal logic of an application’s code. It is performed by development teams.

51. GUI software Testing: The process of testing a product that uses a graphical user interface, to ensure it meets its written specifications. This is normally done by the testing teams.

52. Globalization Testing: Testing method that checks proper functionality of the product with any of the culture/locale settings using every type of international input possible. It is performed by the testing team.

53. Hybrid Integration Testing: Testing technique which combines top-down and bottom-up integration techniques in order leverage benefits of these kind of testing. It is usually performed by the testing teams.

54. Integration Testing: The phase in software testing in which individual software modules are combined and tested as a group. It is usually conducted by testing teams.

55. Interface Testing: Testing conducted to evaluate whether systems or components pass data and control correctly to one another. It is usually performed by both testing and development teams.

56. Install/uninstall Testing: Quality assurance work that focuses on what customers will need to do to install and set up the new software successfully. It may involve full, partial or upgrades install/uninstall processes and is typically done by the software testing engineer in conjunction with the configuration manager.

57. Internationalization Testing: The process which ensures that product’s functionality is not broken and all the messages are properly externalized when used in different languages and locale. It is usually performed by the testing teams.

58. Inter-Systems Testing: Testing technique that focuses on testing the application to ensure that interconnection between application functions correctly. It is usually done by the testing teams.

59. Keyword-driven Testing: Also known as table-driven testing or action-word testing, is a software testing methodology for automated testing that separates the test creation process into two distinct stages: a Planning Stage and an Implementation Stage. It can be used by either manual or automation testing teams.

60. Load Testing: Testing technique that puts demand on a system or device and measures its response. It is usually conducted by the performance engineers.

If would be interested in Aware Testing Services, you can view our Testing Solutions Page.