Software Testing Material

Confuse! What is IPA file? IPA is archived version of iOS Applications. IPA is used for testing purpose, IPA can be shared with each other and can be install into iOS devices like iPhone, iPad, iPod. Application can install only in those devices, which are bind with used provisioning profile to generate the IPA file. Note: Steps remain same for both Mac and Windows. How to Install IPA file in Device? Windows users, please Download iTunes from Apple if you don't have already installed in your machine. Mac users, iTunes should build in your machine, and then also they can Download from Apple . Instructions for Windows a) if you receive an .ipa file: 1. Connect your iPhone/iPod touch/iPad to the computer. 2. Double-click on the .ipa file. This will open iTunes and add the app to your collection. 3. Synchronize your applications. b) If you receive a zip file with a file with “.mobileprovision” extension and a folder containing the app: Do not open the app folder or Windows

Software Development Phases: Information Gathering: It encompasses requirements gathering at the strategic business level. Planning: To provide a framework that enables the management to make reasonable estimates of Resources Cost Schedules Size Requirements Analysis: Data, Functional and Behavioral requirements are identified. Data Modeling: Defines data objects, attributes, and relationships. Functional Modeling: Indicates how data are transformed in the system. Behavioral Modeling: Depicts the impact of events. Design: Design is the engineering representation of product that is to be built. Data Design: Transforms the information domain model into the data structures that will be required to implement the software. Architectural design: Relationship between major structural elements of the software. Represents the structure of data and program components that are required to build a computer based system. Inter

      1 . Test early and test often. 2 . Integrate the application development and testing life cycles. You'll get better results and you won't have to mediate between two armed camps in your IT shop. 3 . Formalize a testing methodology; you'll test everything the same way and you'll get uniform results. 4 . Develop a comprehensive test plan; it forms the basis for the testing methodology. 5 . Use both static and dynamic testing. 6 . Define your expected results. 7 . Understand the business reason behind the application. You'll write a better application and better testing scripts. 8 . Use multiple levels and types of testing (regression, systems, integration, stress and load). 9 . Review and inspect the work, it will lower costs. 10 . Don't let your programmers check their own work; they'll miss their own errors.

What is configuration management? Our systems are made up of a number of items (or things). Configuration Management is all about effective and efficient management and control of these items. During the lifetime of the system many of the items will change. They will change for a number of reasons; new features, fault fixes, environment changes, etc. We might also have different items for different customers, such as version A contains modules 1,2,3,4 & 5 and version B contains modules 1,2,3,6 & 7. We may need different modules depending on the environments they run under (such as Windows NT and Windows 2000). An indication of a good Configuration Management system is to ask ourselves whether we can go back two releases of our software and perform some specific tests with relative ease. Problems resulting from poor configuration management Often organisations do not appreciate the need for good configuration management until they experience one or more of the probl

VOLUME TESTING:    To find the weakness in the system with respect to its handling of large amount of data, during short time period. ( focus is amount of data) STRESS TESTING:  The purpose of stress testing is, to test the system capacity, whether it is handling large number of processing transactions during peak periods. (moment) CONCURRENCY TESTING:  It is similar to Stress Testing, here we are checking the system capacity to handle large number of processing transactions in an INSTANT. PERFORMANCE TESTING:  System performance can be accomplished in parallel with volume and stress testing, because system performance is assessed under all conditions.  System performance is generally assessed in terms of response time and throughput rates, under different processing and configuration condition. REGRESSION TESTING: Is the re-execution of same subsets of test cases that have already executed, to ensure that changes(after defect fix) have not propagated unintended sid

      Writing test cases to all possible checks is irrelevant.  So we can reduce the number of test cases by avoid some unwanted checks.  To reduce the number of test cases, there are three methods to be followed. 1. Equivalence Class Partitioning (ECP) 2. Boundary Value Analysis (BVA) 3. Cause Effect Graphing (CEG) Equivalence Class Partitioning (ECP): ECP is a black box testing method that divides the input domain of program into classes of data, from which test cases can be derived.  It uncovers classes of errors, there by reducing the total number of test cases that must be developed. Group of tests forms equivalence class if, They all tests the something If one test finds a defect, the others will If one test does not find a defect, the others will not. Tests are grouped into one equivalence class when  They affect the same output variables They result in similar operations in the program They involve the same input variables Process of findin

Error: It refers to the discrepancy between computed or measured value and theoretically correct value. i.e. Difference between actual output and correct output of the software. Fault:   Fault is the basic reason for software malfunction. i.e. Fault is a condition that causes a system to fail in performing its required function. Failure: Is the inability of the system or component to perform a required function according to its specifications.  A Software failure occurs if the behavior of the software is different from the specified behavior. Bug :  Non Functionality to a functionality Presence of an error implies that a failure must have occurred, and the observance of a failure implies that a fault must be present in the system. During the testing process only failures are observed by which presence of fault is deduced.  The actual faults are identified by separate activities commonly referred to us 'debugging'. In other words, for identifying faults afte

Reason for testing parts separately is that if a test case detects an error in a large program, it will be extremely difficult to pin point the source of error. It is difficult to construct test cases so that all the modules will be executed.  This may increase the change of module's error undetected. What is the need for independent testing/ third party testing ? Sometimes error occurs because the programmer did not understand the specification clearly.  Testing of a program by its programmer will not detect such errors, but independent testing may succeed in finding them. Time concern If the customer want the third party testing Non-availability of testing resources It is not easy for someone to test their own program with proper frame of mind for testing. What is the Testing Principles?             1. All the test cases should be traceable to the customer requirements.             2. Testing should be planned long before testing begins.             3. Tes

As per ANSI/IEEE standard 729 the following are the five level of defect classification are 1. Critical: The defect results in the failure of the complete software system, of a subsystem, or of a software unit (program or module) with the system. 2. Major : The defect results in the failure of the complete software system of a subsystem, or of a software unit (program or module) within the system. There is no way to make the failed components, however, there are acceptable processing alternatives which will yield the desired result. 3. Average : The defect does not result in a failure, but causes the system to produce incorrect, incomplete, or inconsistent results, or the defect impairs the systems usability. 4 . Minor: The defect does not cause failure, does not impair usability, and the desired processing results are easily obtained by working around the defect. 5. Cosmetic: The defect is the result of non-conformance to a standard, is  related to the aesthe