What is SDLC? Initial : Meeting between business Analyst and Client.

Project initiation note(PIN) is prepared by project manager and submitted for approval to C.E.O Budget Issues (business issues are discussed) The output of initial state is BRS BRS : Rough Effort Estimation(Manpower, Schedule, Cost) Overview of the project. Customer requirements. (Functional) Customer Expectations. (Performance, Security, Usability) Requirements analysis gathering: All the customer requirements and expectations are gathered and analyzed in this phase. All the customer requirements are transformed to system requirements. Effort Estimation. Business model is build. Technology is decided. One copy of SRS goes to designing and another to testing. Designing: HLD: It consists of overall architecture of the application from root module to leaf module. LLD: It consists of architecture and business flow of internal working of sub modules. DFDs, Algorithms, Flowcharts, E-R diagrams, Network diagrams, and pictorial representation represent these. Output of Design face is called technical design document or functional design document or pseudo code. Coding: In this phase pseudo code is converted to machine-readable format using appropriate technology. The output this phase is .exe module. Testing: This exe module is tested with the test cases, if any bugs are found they are reported and this process is continued till the application is reasonably bug free. Maintenance: In this phase the application goes into production. What is Compiled Module? It is a test script that contains a library of user-defined function, which are called from with in other tests. The Functions are interpreted compiled and ready for execution before start your test session. What is Data Base Testing? To check the Validation and Integrity of Database we go for Database Testing. Validation: To check whether data entered in the front-end application is correctly saved in database. Integrity: If data entered to front end has to be saved in database in more than two tables, then we have to check corresponding tables are updated.

Bug life cycle: Track the Bug. Log the Bug in DTS.

Give the Severity and Priority. Give status as open. Assign this Bug to test lead. Test Lead reviews the bug and assigns status to the Bug. Open- goes to development team. Rejected- comes to us. Deferred- next version. After the status is open this bug and Resolve the bug and gives the development team. Development team reviews the bug and resolve the bug and gives the resolution type. Based on this modified build is prepared and send to us. Execute the existing test suit on the modify build. If the bug is Resolved and make the status as closed. If the Bug is not resolved and make the status as Reopen and again assign it to test lead. Status: NEW OPEN REJECTED DEFERRED CLOSED REOPEN Severity: High(1), Medium(2), Low(3). Priority: Urgent(1), High(2), Medium(3), Low(4). Resolution Type: Fixed. Cant be Fixed. Deferred. Pending. Rejected. Functions as Designed. Irreproducible. Need more info. Software Limitations. H/W Limitations. What is Regular Expression? It is a string that specifies a complex search phrase, which enables w/r to identify windows and objects with varying labels and titles. In the Runtime if tables of objects changed then these changes can be handled by using regular exp.

What are Testing Techniques? BVA: It is a Test case design technique that concentrates on the boundary conditions of the input domain of the program. By using BVA test cases are derived based on the size and range of input values. ECP: It is a testing technique that divides input domain of a program into classes of a data from which test cases are derived. Test cases derived using this technique uncover a class of errors. Number of test cases can be reduced reasonably. Valid Invalid

A-Z a-z 0-9 Special characters like !, @, #, $, %, ^, &, *, (, ), _, +. What is Severity and Priority? Severity: The impact of bug on the application is called severity.(it is a tester conscience, it is viewed from tester side) Priority: The time taken to fix the bug or the priority is gives based on Severity. The urgency that bug has to be fixed. Ex:1. high P, low S Error in user interface (spelling mistakes, error messages not clear) Ex: 2. low P, high S Client requirement is 500 records have to be stored in database, but the database is designed such that it can handle up to 700 records. When we enter the records into the database it is storing only 600 records. Though this is not a problem for Client but this is against the design of the database Ex:3. high P , high S Data entered in the front-end of an application is not getting stored in the database. Ex:4. Low S, Low P Font size, field level validations tab order. What is Traceability Matrix? It is mapping between customer requirements and test cases. Traceability Matrix ensures that Test cases written to test a feature of application are able to trace the customer requirements. By using T.M we can come to the conclusion as when complete testing be stopped. What is Static and Dynamic Testing. Static Testing: Static testing is nothing but verification, by static testing we can come to a conclusion that all the customer requirements are traceable by reviewing the test cases. Dynamic Testing: Dynamic Testing is actual testing of application by executing the test cases on the application. It is also called as validation.

Client /Web application? Client server is 2-tier Usability, functionality, performance, security Limited users Database server available. Web application: It is n-tier. Usability, Functionality, Performance, Security(load, stress, volume) Unlimited users. Database server will be Remote place. Security Testing is compulsory Authorization. Access control. Session ids.

Links Testing. (main link, broken link.) Cross-Browser Testing (different browsers) Compatibility Testing. Database Testing. What is Data Driven Test? It is an automated testing approach in which navigation and functionality of a test script is driven by external data. It involves parameterizing test script Parameterization: Replacing fixed values or constants in TSL statements with parameters, these parameters are stored in a data table within corresponding values. Whenever a features of for application needs multiple set of values (multiple iterations) then parameterize the test. The fixed values from the application is replaced by value from the data table in each iteration. Data Driven Script: Table= default.xls; ddt_open(table, DDT_MODE_READ/READWRITE); If (rc!=E_OK && rc!=E_FILE_OPEN); pause(cant open table); ddt_get_row_count(table,a); for(b=1; b<=a; b++) { ddt_set_row(table, b); tsl statements edit_set(logical name, ddt_val(table, column_name)) } ddt_close(table);

What is System Testing? To test the overall functional requirements of an application. Usability Testing: User Interface. Ease to Use Look and Feel Cosmetic check(background color, alignment, font) Services levels Manual Support Meaningful Error Messages. Functional Testing: 1. Functionality Testing. Behavioral Coverage. Input Domain Coverage. Calculation Coverage. Error Handling Coverage. Data Base Coverage. Data Format is correct or not. 2. Input Domain Coverage. E.C.P B.V.A 3. Recovery Testing: To check how well an application recovers from system crashes, hardware and other catastrophic problems.

4. Installation Testing: To check installation of the application is easy and correct. 5. Configuration Testing: To check application runs in different hardware configurations and network devices. 6. Compatibility: To check app runs on different platforms(os). 7. Inter System Testing: Co-existence with other softwares to share the resources properly. 8. Parallel Testing: Comparing our app with existing application in the market. Security Testing: Authorization: Is the User valid to access the application. Access control: Valid user has the right permission to use a specific service. Encryption/Decryption: Performance Testing: Performance Testing: Performance testing to check the transaction time, response time of an application under loads. Load Testing: Subjecting a system to reasonably heavy loads to check at what point of time the application performance degrades. Stress Testing: Subjecting system to unreasonably heavy loads while denying the resources(RAM, Interrupts, Hard disk, etc.,) needed to process this load. The system is expected to crash, the system should recovers from this crash in decent manner. Volume Testing: Giving huge volumes of the data to the application to check application of performance. Data Storage Testing: Amount of the data can be stored. What are contents in DTS? 1. Bug ID 2. Bug Description 3. Application version ID 4. Application Feature 5. Test case 6. Reproducible or not 7. Status 8. Severity 9. Priority 10. Bug detected by 11. Bug detected on 12. Assign to 13. Fixed by 14. Resolved by 15. Resolved on 16. Resolution Type What are Test Plan Contents? 1. Introduction 2. Scope and Objective 3. Features to be tested 4. Features not to be tested 5. Test deliverables 6. Test Exist Criteria 7. Test Resumption Criteria 8. Test Suspension Criteria 9. Test schedule 10. Roles and Responsibilities

11. 12. 13. 14.

Resources (h/w, s/w) Risks and mitigations Test metrics Approvals

What are the Test Deliverables? Test Deliverables are documents that are given to customer at the sign off. They are 1. Test plan 2. QA documents. 3. Test cases 4. Test Results. 5. Test Script. 6. Defects. 7. Test Summary Report. 8. Status Reports (weekly/monthly)

What are the Test Case Contents? 1. Test Case name 2. Test Case ID. 3. Test Use case. 4. Test Pre-conditions. 5. Test Scenario(module). 6. Test input data. 7. Test Description(steps). 8. Manual/Automated. 9. Expected Results. 10. Actual Results. 11. Results. 12. Tester name. 13. Remarks. What is difference between Product and Project (Application)? Product: Requirements are gathered by company it self-based end users needs. It involves long term Testing. Testing is conducted at customer site by end users. Testing is conducted in real environment. Project: The customers exclusively give requirements. It involves limited testing. Testing is conducted at developers site. Testing is conducted in virtual environment. What is the difference between Debugging and Testing? Testing aims at finding an error where as Debugging is the process that results in the removal of the error. Debugging occurs a consequence of successful testing. What is Verification and Validation Verification: Verification typically involves Reviews and meeting to evaluate code, design documents, Requirement specification testing documents (test plan, test case) etc., this is done by check lists, issue lists, inspection and walkthroughs. Verification: Are we building the product right?

Validation: Validation is actual testing of the application. It is always followed by verification. Validation: Are we building the right product? What is Regression Testing? Re-testing an application to check whether there are any cropped up bugs in an application after necessary modifications and enhancements have been done. After the bugs in an application are rectified, after any enhancements have been made to the application we execute the existing test suite on the application to check these enhancements and modifications made to the application does not effect other parts of the application. Automation tools are mainly used for regression testing. What are the CMM Levels? 1. Initial. 2. Repeatable. 3. Defined. 4.Managed. 5.Optimized. KPA: Key Process Areas(KPAs) are defined by a set of key practices and key indicators. Key practices are policies, procedures and activities that must occur before a KPA is fully instituted. Key indicators are those key practices that ensure that all the goals of KPA are achieved. 1). Initial: Ad-hoc procedures/own procedure, Should have efficient Team. 2). Repeatable: Well-defined process, Key processes are repeatable. 3). Defined: Objective evidence, everyone should record their activities, everyone should adhere to quality standards. 4). Managed: Measurements and Metrics, Quantifying objective criteria. 5). Optimized: R&D (Research & Development), Continuous improvement of the product KPAs are additive. There are 18 KPAs. They are: 1. Software Configuration Management. 2. Software Quality Assurance. 3. Software subcontract Management. 4. Software project tracking and oversight. 5. Software project planning. 6. Requirements management. 7. Peer Reviews. 8. Inter-group co-ordination. 9. Software product engineering. 10. Integrated Software Management. 11. Training Program. 12. Organization process definition. 13. Organization process focus. 14. Software Quality Management 15. Quantitative Process Management. 16. Process change Management. 17. Technology change Management. 18. Defect Prevention. CMM-Level 2: 1-6 KPAS should be satisfied. CMM-Level 3: 1-13 KPAS should be satisfied.

CMM-Level 4: 1-15 KPAS should be satisfied. CMM-Level 5: 1-18 KPAS should be satisfied.