Software Testing Concepts
Acceptance testing: Formal testing conducted to enable a user, customer, or other authorized entity to determine whether to accept a system or component.
- Ad hoc testing: Ad hoc testing carried out using no recognized test case design technique
- Alpha testing: Alpha Testing simulated or actual operational testing at an in-house site not otherwise involved with the software developers
- Backus-Naur form: Backus-Naur form is a metalanguage used to formally describe the syntax of a language
- Beta testing: Beta testing is Operational testing at a site not otherwise involved with the software developers
- Big-bang testing: Big bang testing is part of Integration testing where no incremental testing takes place prior to all the system’s components being combined to form the system
Software Testing Process
The most visible a part of testing is death penalty tests. But to be effective and economical, test plans should also include time to be spent on planning the tests, designing test cases, preparing for execution and evaluating status.
The fundamental take a look at method consists of the subsequent main activities:
- planning and control
- analysis and design
- implementation and execution
- evaluating exit criteria and reporting
- test closure activities
Although logically sequential, the activities in the process may overlap or take place concurrently.
Software Test plan and control
Test planning has the following major tasks:
- crucial the scope and risks, and identifying the objectives of testing
- crucial the take a look at approach (techniques, test items, coverage, distinctive and interfacing the groups concerned in testing, testware)
- Determining the required test resources (e.g. people, test environment, PCs)
- Implementing the take a look at policy and/or the take a look at strategy
- Scheduling test analysis and design tasks
- Scheduling test implementation, execution and evaluation
- Determining the exit criteria
Test control has the following major tasks:
- measuring and analyzing results
- watching and documenting progress, take a look at coverage and exit criteria
- initiation of corrective actions
- making decisions
Software Testing Analysis and Design
Test analysis and style is that the activity wherever general take a look rating objectives square measure remodeled into tangible take a look at conditions and test styles.
Test analysis and style has the subsequent major tasks:
- Review and analyze the requirements, architecture, design, interfaces and etc
- Identifying Test Scenarios,test conditions,test requirements and also required test data based on analysis of test items, the specification, behavior and structure
- Coming up with the take a look at cases supported the take a look at situations or take a look at Conditions
- Evaluating test-ability of the requirements and system
- Take a look at setting set-up and distinctive any needed infrastructure and tools
Software Test design implementation and execution
Software Test design implementation and test execution is the activity where test conditions are transformed into test cases and testware, and the environment is set up.
Test Design implementation and Test execution has the following major tasks:
- Developing and prioritizing take a look at cases, creating test data, writing test procedures and preparing test harnesses and writing automated test scripts
- Creating test suites from the test cases for efficient test execution for different cycles
- Verifying that the test environment has been set up correctly which mans latest build deployed or not
- Take a look at cases either manually or by mistreatment take a look at execution tools, according to the planned sequence
- Work the end result of take a look at execution and recording the identities and versions of the package underneath take a look at, take a look at tools and testware
- Comparing actual results with expected results
- Reporting discrepancies as incidents and analyzing them in order to establish their cause like defects in the code, in specified test data, in the test document, or a mistake in the way the test was executed)
- Repeating test activities (Regression) as result of action taken for each discrepancy. For example, re execution of a test that previously failed in order to confirm whether fix is working properly or not, and also test related functionality which is regression testing whether new fix effecting exiting functionality or not
