본문 바로가기

syllabus

4.3 Specification-based or black-box techniques (명세 기반 기법 또는 블랙 박스 기법) Terms Boundary value analysis, decision table testing, equivalence partitioning, state transition testing, use case testing. 4.3.1 Equivalence partitioning inputs to the software or system are divided into groups that are expected to exhibit similar behavior, so they are likely to be processed in the same way. equivalence partitions (or classes) can be found for both valid data and invalid data,.. 더보기
4.1 The Test Development Process (테스트 개발 프로세스) Terms Test case specification, test design, test execution schedule, test procedure specification, test script, traceability BackgroundThe process described in this section can be done in different ways, from very informal with little or no documentation, to very formal (as it described below). The level of formality depends on the context of the testing, including the organization, the maturity.. 더보기
3.3 Static analysis by tools (툴에 의한 정적 분석) Terms Compiler, complexity, control flow, data flow, static analysis. BackgroundThe objective of static analysis is to find defects in software source code and software models.Static analysis is performed without actually executing the software being examined by the tool; dynamic testing does execute the software code. Static analysis can locate defects that are hard to find in testing. As with .. 더보기
3.2 Review process (리뷰 프로세스) TermsEntry criteria, formal review, informal review, inspection, metric, moderator/inspection leader, peer review, reviewer, scribe, technical review, walrthrough. BackgroundThe different types of reviews vary from information (e.g. no written instructions for reviewers) to very formal (i.e. well structured and regulated). 3.2.1 Phases of a formal review A typical formal review has the following.. 더보기
3.1 Static techniques and the test process (정적 기법과 테스트 프로세스) Terms Dynamic testing, static testing, static technique. BackgroundUnlike dynamic testing, which requires the execution of software, static testing techniques rely on the manual examination (reviews) and automated analysis (static analysis) of the code or other project documentation. Reviews are a way of testing, which requires the execution of software, static testing techniques rely on the man.. 더보기
2.3 Test Types (테스트 유형) Terms Black-box testing, code coverage, functional testing, interoperability testing, load testing, maintainability testing, performance testing, portability testing, reliability testing, security testing, specification-based testing, stress testing, structural testing, usability testing, white-box testing Background a group of test activities can be aimed at verifying the software system (or a .. 더보기
1.5 - The psychology of testing (테스팅 심리학) TermsError guessing, independence. Backgroundthe mindset to be used while testing and reviewing is different to that used while developing software With the right mindset developers are able to test their own code, but separation of this responsibility to a tester is typically done to help focus effort and provide additional benefit. such as an independent view by trained and professional testin.. 더보기

티스토리툴바