Neeraj's Blog

Capibility Maturity Model or CMM is well defined process for determining maturity level of any organization.This model is defined in 5 different stages. 1. Initial : At this level no process is defined for any work.everything is done on adhoc basis.Management is involved at every place.If someone is doing part A of any Project using their own standard & measurement & this is given to some other group to complete part B, second group is not forced to adhere process & measurement followed by group A,they implement their own understanding about the product.At this level any kind of document or specification is hardly maintained or available.There are no means available to measure output of the final product. In view of a tester working in this level is most difficult task.As product is developed day to day basic & there is no mechanism to track previous changes , its increase workload on tester.Most of the testing is done during development phase ...

Software Development Life Cycle : Software is built rather we should say that software is engineered in various phases.As soon as one phase is complete we move on to another phase or we can work with two different phases hand in hand.These phases start with from requirement gathering from client & goes till maintenance of this project. SDLC is lifecycle of these various different phases form top to bottom. Various part of SDLC are : 1.Planning 2. Requirement Gathering 3. Designing 4. Coding 5. Integration & Testing 6. Installation & Acceptance 7. Maintenance Software Tetsing Life Cycle: STLC is part(Phase) of complete software development life cycle.In this phase we ensure that the product we building is as per requirement given by client or not.This phase start from Requirement Study & ends with till the exit criteria of testing is meet. Various part of STLC are : 1. Requirement Gathering/Study 2. Test Case Planning 3. Tes...

Test Plan 1. Introduction 1.1 Overview of System 1.2 Purpose of this Document 1.3 Audience 2. Scope of the Testing and Test Strategy 2.1 Scope of the Testing 2.2 Test Strategy 3. Test Process 4. Test Approach 4.1 Full Test Cycle 4.1.1 Build Verification Test (Smoke Test) 4.1.2 Defect Verification 4.1.3 Functional Test Pass 4.1.4 Performance & Stability Test 4.1.5 Regression Test 4.2 Daily Builds 4.2.1 Basic Test 4.2.2 Basic Performance Test 5. Test Criteria 5.1 Test Entry Criteria - Release note has been issued - Release note stating the builds information, build deployment information, Defects that have been fixed, open issues - Builds are available on staging - Unit test and integration test results are attached - Test Environment is completely ready - Req Specification is available in case any changes 5.2 Test Exit Criteria - Certification by the QA that all Severity 1 and Severity 2 problems have been fixed - Complete of the execution...

2-tier architecture: In 2-tier, the application logic is either buried inside the User Interface on the client or within the database on the server (or both). With two tier client/server architectures (see Two Tier Software Architectures), the user system interface is usually located in the user's desktop environment and the database management services are usually in a server that is a more powerful machine that services many clients. Processing management is split between the user system interface environment and the database management server environment. The database management server provides stored procedures and triggers. 3-tier architecture : In 3-tier, the application logic (or) process lives in the middle-tier, it is separated from the data and the user interface. 3-tier systems are more scalable, robust and flexible. In addition, they can integrate data from multiple sources. In the three tier architecture, a middle tier was added between the user system interfac...

Verification:  Have we built the software right? (i.e., does it match the specification). Verification is a Quality control process that is used to evaluate whether or not a product, service, or system complies with regulations, specifications, or conditions imposed at the start of a development phase. Verification can be in development, scale-up, or production. This is often an internal process. The review of interim work steps and interim deliverables during a project to ensure they are acceptable. To determine if the system is consistent, adheres to standards, uses reliable techniques and prudent practices, and performs the selected functions in the correct manner. Performed during development on key artifacts, like walkthroughs, reviews and inspections, mentor feedback, training, checklists and standards.Verification is static in nature. Validation: Have we built the right software? (i.e., is this what the customer wants). Validation is a Quality assurance process of es...