ISTQB (Temel Yazılım Testi)

Establishes a foundation for the course, provides a workable definition of software quality and shows how testing fits into the overall quality process. 

Testers follow the same basic process that scientists use; we follow the principles of experimentation and measurement. In this course, we map your testing method back to those principles and show
how, at each step in your testing, you’re making complex decisions about what to test and how to test it. Utilizing a combination of skills, tactics, practices, and tools - this section helps build a base that testers in any context (of any skill level) can apply to solve testing problems.
1. Model the Testing Space. Compose, describe and work with visual models of the software to identify relevant dimensions, variables, and dynamics so you can develop an effective test
strategy.
Determine Test Coverage. Understand a variety of common measures of test coverage and
choose the most appropriate ones for each project; determine the scope of testing; establish a structure to track test coverage
Determine Test Oracles. Identify the sources of truth to determine whether the application has passed or failed tests; review common formal and heuristic oracles
Determine Test Procedures. Define what test procedures and test cases are; identify common test procedure types; learn how to document test procedures in a practical, efficient manner
Configure the Test System. See how to ensure you have everything needed to support testing; discuss common challenges to test configuration; consider test lab requirements and realities
Operate the Test System. Learn how to manage tester contact with the application under test (AUT); discuss different methods of interaction with the system to address different testing objectives; identify common artifacts and practices related to test operation
Observe the Test System. Learn what empirical data to capture about the application under test and how to preserve testing interactions for review and reproducibility; consider common
tools used to assist with test observation; identify common problems and human tendencies related to observation
Evaluate Test Results. Discuss possibilities and probabilities related to test results (not every test failure is a bug!); identify typical test result evaluation tasks; consider performance test
results interpretation; learn key factors related to defect communications
Report Test Results. Learn how to make credible, professional reports of testing results and testing progress that address the varied needs of your target audiences; identify guiding
principles for report design; review best practices and examples for defect reporting, progress status reporting, and quality statistics reporting

The heart of good testing is coming up with good test cases. In this section, we will define what makes test cases “good”, and discuss these strategies for identifying test cases in specific contexts:
1. White Box strategies
2. Black Box strategies
3. Input and data-based strategies
4. User interface oriented strategies
5. Business Process flow strategies
6. Strategies based on your personal and organizational experiences

Different testing activities take place as the software progresses through its life cycle. (Agile testers perform these same testing activities, even though they are not project phases.) This section explains the common phases of software testing, including the purpose of each, who normally performs it, and the typical types of tests that are done.
Test phases or types discussed:
1. Unit and Software
2. Integration
3. System and System Integration
4. Product Readiness
5. Regression
6. User Acceptance 

Different approaches to testing are used to address different testing objectives and different project conditions. Some approaches are more formal, lengthy, traceable, and reproducible. Others are more free-form, quicker, less traceable, and less reproducible. The range of such approaches forms a continuum from which testers select the optimal combination for a given project. The best selection of approaches addresses the needs for both positive and negative testing.
1. The Testing Approach Continuum
2. Scripted Testing
3. Freestyle Testing
4. Middle-Ground (Charters, Checklists, Scenarios)

Without question, functional testing is a must-have for software quality. However, there’s more to the picture than that. This section describes several key types of non-functional testing and identifies,
what their scope is, and what techniques or best practices apply.
1. Performance
2. Usability
3. Accessibility
4. Security
5. Portability
6. Localization