Software Testing

Software testing.

[Audio] Test planning Test planning is the activity of verifying the mission of testing Involves identification of objectives and specifications of test activities to meet the objectives and mission.

[Audio] Tasks involved in test planning  Determine scope of the project  Determine risks on the project  Identify the objectives of testing  Determine the test approach, test techniques, test items, coverage, identify teams and so on  Determine the resources required – People – Infrastructure – Test environment.

[Audio] Tasks involved in test planning Implement test strategy Schedule Test analysis and designs tasks Implementation, execution and evaluation Determine exit criteria.

[Audio] Test control  Test control is an ongoing activity involved in monitoring progress of the project comparing the actual against the planned  Involves in taking actions to meet the mission and objectives of the project.

[Audio] Tasks involved in test control  Measure and analyze results  Monitor and document Progress Test coverage Exit Criteria  Initiate corrective actions  Make decision.

[Audio] Test Analysis  Test Analysis can be defined as a technique of analyzing or reviewing the facts that form the foundation upon which software testing is conducted..

[Audio] Test Analysis and Design  Test analysis and design involve – Review Specifications(detailed description of the testing) Architecture Design Interfaces – Identify Determine what is to be tested (identify test conditions) – Design test cases Determine how and what is to be tested (design test cases) – Build tests Implement tests (data, scripts etc.,) – Design test environment Identify and setup required infrastructure and tools.

[Audio] Test case  A test case is a document that describes an input, action, or event and an expected response, to determine if a feature of an application is working correctly.

C phe r Test Case ID TC 01 TC 02 TC 03 TC 04 TC 05 Pla i n Tex t Test Case Objective Test Caesar Cipher Algorithm (For Encryption) Test Caesar Cipher A I gori thm (For Decryption) Test Vignere Cipher Test MDS Test co I umner Cipher Text Steps Pre requisite Textfield should be enabled Textfield should be enabled Text Fields should be enabled Text Fields should be enabled Text Fields should be enabled I. Select Encrypt Button 2- Enter Plain Text 3. Enter Numeric Key 4 _ Submit I Select Decrypt Button Key Input Data P: hello C: khoor P: hello K: abcds 2- 3- 4. 2- 3- 1. 2- 2. 3. Enter Cipher Text Enter Numeric Key Submit Enter Plain Text Enter String Key Submit Enter Plain Text Submit Enter Plain Text Enter Numeric Key Subrnit T: P: hello hello Expected Output khoor hel 10 h fnog 5d41402a bc4b2a76 b9719d91 1017c592 hleol Actual Output khoor hello fhgon 5d41402a bc4b2a76 b9719d91 1017c592 hleol Status PASS PASS FAIL PASS PASS.

[Audio] Typical Test Case Parameters  Test Case ID  Test Scenario  Test Case Description  Test Steps  Prerequisite  Test Data  Expected Result  Test Parameters  Actual Result  Environment Information  Comments.

[Audio] A good test case….,  Effective (Finds faults)  Exemplary (Representative)  Evolvable (Easy to maintain)  Economic (Cheap to use).

[Audio] Design Test cases  Determine expected result Outcome of each test case should be predicted What is the outcome What is changed What is not changed  Design set of tests  Design test inputs and test data.

[Audio]  List the conditions that should be tested.  Use the test design techniques specified in the test plan.  There may be many conditions for each system function or attribute.  Priorities test conditions.  Ensure that most important conditions are covered..

[Audio] Activity 1. What are the objectives and task include in test plan ? 2. What are the purpose of test control and it's task ? 3. What are the importance of test analysis ? 4. What are the purpose of using test case and characteristics of good test case?.

[Audio] Build Test Cases  Test Case - Contains specific data values for a scenario to be executed under specific conditions to produce a predicted result.  Test Script - A set of instructions that define each step to be taken and the expected results of each step.  Prepare test scripts Less system knowledge tester has the more detailed the scripts will have to be  Prepare test data Test data should be existent for all the test cases to be executed  Expected result should be available Should be defined before the test is executed.

[Audio] Test design  Test design is a process that describes "how" testing should be done. It includes processes for the identifying test cases by enumerating steps of the defined test conditions..

[Audio] Identify Test Design Activities Test Design activities are comprise of 1. Preparation of test plan 2. Review requirement documents 3. Designing & Review High level test cases 4. Designing & Review detailed test cases 5. Execution of test cases 6. Report test results 7. Analyze test results.

[Audio] 01.Preparation of test plan  The way of prepare document that describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, the features to be tested, the testing tasks, who will do each task, degree of tester independent, the test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice, and any risks requiring contingency planning. It is a record of the test planning process..

[Audio] 02. Review requirement documents  To prepare effective test cases, testers and QA engineers should review the software specification documents [SRS] carefully and raise as much queries as they can..

[Audio] 03. Designing & Review High level test cases  These test cases define the functionality of a system/module in a broader, without getting into the practical details of the scenarios or into sense the depth of the functionality. Qualification`  For a example web based application that requires user to login, a high-level test case could be "User should be able to Login with correct credentials(Qualification).

[Audio] 04. Designing & Review detailed test cases (Low-Level Test Cases)  These test cases define the functionality/scenario in extensive detail. These test cases are more refined and are generally written with details such as Expected Result Test Data etc For a example web based application that requires user to login, a low-level test case could describe the URL of the Login page, the UI of the Login page (username and password text boxes, login button, forgot password link), etc. along with the proper test data..

[Audio] 05. Execution of test cases  Create a test case. A test case is required for test execution.  Add the test case to a test plan. A test plan helps to organize your test execution activities, but it is not a requirement for test execution. create a test script and associate it with the test case.  Create a test execution record for the test case or generate multiple test execution records for the test case automatically..

[Audio]  Run the test execution record.  View the test execution results and file defects as needed.  Update the test execution results as needed and save the results..

[Audio] 06. Report & Analyze test results  The Test Analysis Report, records results of the tests. presents the capabilities and deficiencies for review, and provides a means of assessing software progression to the next stage of development or testing..

[Audio] Testing Process. Testing Process.

[Audio] Test implementation, execution & verification Test implementation and execution is the activity where test procedures or scripts are specified by combining the test cases in a particular order and including any other information needed for test execution, the environment is set up and the tests are run..

[Audio] Tasks involved in implementation and execution are  Prioritize test cases  Develop test cases  Develop test data  Prepare test scripts  Create test suites  Verify if the test environment is set up properly  Execute test case as per the schedule  Manual execution  Automated.

[Audio]  Test results should be recorded  Follow the plan  Mark the status of the test case as it is being executed  Document actual outcome from the test  If you get any new ideas to test record them  Record is used to certify that all the tests have been carried out  Compare actual outcome with the expected outcome and log the discrepancies  Software fault  Version fault  Test run incorrectly  After the fault is fixed repeat the test activities once again.

[Audio] Entry Criteria & Exit criteria. Entry Criteria & Exit criteria.

[Audio]  What is an Entry Criterion?  Entry criterion is used to determine when a given test activity should start. It also includes the beginning of a level of testing, when test design or when test execution is ready to start.  Examples for Entry Criterion:  Verify if the Test environment is available and ready for use.  Verify if test tools installed in the environment are ready for use.  Verify if Testable code is available.  Verify if Test Data is available and validated for correctness of Data..

[Audio]  What is an Exit Criterion?  Exit criterion is used to determine whether a given test activity has been completed or NOT. Exit criteria can be defined for all of the test activities right from planning, specification and execution.  Exit criterion should be part of test plan and decided in the planning stage.  Examples of Exit Criteria:  Verify if All tests planned have been run.  Verify if the level of requirement coverage has been met.  Verify if there are NO Critical or high severity defects that are left outstanding.  Verify if all high risk areas are completely tested.  Verify if software development activities are completed within the projected cost.  Verify if software development activities are completed within the projected timelines..

[Audio] Major tasks involved in test closure activities  Verify whether all the planned deliverables are delivered  Test Plans  Test Cases  Test scripts  Test results  Archive the test ware, environment and infrastructure for later use  Ensure that all defects are closed and any opened defects have found appropriate change records  Acceptance is signed off.

[Audio] Activity 1. what are the different between design test case and build teat case? 2. List down the test design activities? 3. Explain the testing process of a system? 4. What's the difference between test plan and test design?.