Explaining about Test plan components of STLC..?

• here we discussing about components of test plan document in STLC process.
• After completion of Test strategy preparation,Test lead concentrating on prepared plan document with the help of project manager and test manager.
• It is detailed plan of the testing requirements like scope,approach,resources and schedules.
• While preparing test plan document,test lead follow IEEE A 29 format.
• The plan consists of

1. Project Overview
2. References
3. Scope
4. Test Strategy
5. Test environment
6. Test deliverable's
7. Staffing plan(Roles & Responsibilities)
8. Risks & Assumptions
9. Milestones
10. Approvals

Explaining about Test strategy and these components..?

• Test Strategy document is a high-level document and developed by test engineer with the help of project manager.this document defines software testing approach to achieve testing objectives.
• Test strategy normally developed from B.R.S document and it is static document.
• In some companies,includes the test strategy inside the test plan.it is mostly for small projects.but for long projects,there is one test strategy document and number of test plans for each phase.
• components of the test strategy document are shown below:

1. Scope and objectives
2. Business issues
3. Roles and responsibilities
4. Communication and status reporting
5. Test deliver-ability
6. Industry Standards to follow
7. Test automation and tools
8. Testing measurements and metrics
9. Defect reporting and tracking
10. Training plan

Explaining about Software Testing Life Cycle( STLC ).?

• while conducting a system testing,to conduct a testing on application test engineers can follow SDLC process.
• STLC process in different stages.They are shown below:

1.Test Strategy

2.Test Plan

3.Test analysis

4.Test Design

5.Test Execution

6.Test Closure

Explaining briefly about Non-Functional System Testing..?

Here,we discussing about non-functional system testing and these types.

• Non-Functional System Testing:

          - it is a special type of testing performed to test the non-functional requirements like response time,portability,stability etc.

          - after completion of functional system testing,test engineers concentrating on Non-functionality of an application.

          - while conducting non-functional system testing,we should concentrating on expectations of customer like 

1. GUI Testing
2. Usability Testing
3. Compatibility Testing
4. Hardware Configurable Testing
5. Performance Testing
6. Inter System Testing
7. Security Testing
8. Installation Testing
9. Recovery Testing
10. Complex Testing.

Explaining about Functional System Testing..?

Here,we discussing about functional system testing and these sun-testings.

• Functional System Testing:

          - Customer requirements or validating functional business requirements of the system is called "Functional System Testing ".

          - While connecting system testing,Test engineers first concentrating on functionality of the application.

          - To check functionality,Test engineers concentrating on functional system testing.

          - During this test,testers concentrating on below sub-testings...

1. Input Domain Testing
2. Output Domain Testing
3. Error Handling Testing
4. Database testing
5. Smoke Testing
6. Real Testing
7. Re Testing
8. Regression Testing.

Explaining about Black-box Testing Techniques and these advantages & disadvantages.?

Here,we discussing about black-box testing techniques and black-box testing usages and disadvantages.

BLACK-BOX TESTING TECHNIQUES:

                         following are some techniques that can be used for designing black-box testing.

1. Equivalence Class Partitioning(E-C-P)
2. Boundary Value Analysis(B-V-A)
3. Decision Table Testing
4. State Transition Testing
5. Error Guessing
6. Use-case Guessing

Explaining about Black-box testing { System Testing and User acceptance Testing }..?

Here,we discussing about block-box testing types and information of those types.

- After completion of white-box testing,testing conducted on application by test-engineer's or by domain experts or customers to ensure the requirement coverage.

- does the application developed as per the customer requirements or not i,e called block-box testing.

- it is also called as "Specification based testing".

- this testing is the combination of system testing and user acceptance testing.

System Testing:

   - To cover all possible operations,we have to conduct both positive and negative testings.

      A. Positive testing:

          --> application check with positive data or testing conducted on application with positive perspective to check what's system supposed to do is called "Positive Testing".

          --> positive testing conduct for entering data is valid or not.

      B. Negative testing:

          -->testing conducted on application with a negative perspective to determine what system not suppose to do is called Negative Testing.

          --> negative testing conduct for find the defects/errors.

Note:

  - these system testing conducting on application,not in programming by Test engineers.

Explaining about Unit Testing & Integration Testing..?

Here,we discussing about unit testing and supporting techniques..

Unit Testing:

      - A smallest testable portion in the source-code of the application is called Unit testing.

      - Individually every program working or not OR conducting testing on each & every program individually,it's called Unit Testing.

      - while conducting unit testing, Programmers follow below white-box testing techniques,

         i,e...

                 1. Basic path coverage

                 2. Control structure coverage

                 3. Program technical coverage

                 4. Mutation coverage

- To conduct above Testing,programmer follow syclo-metric of complex pattern.

Integration Testing:

      - After completion of Unit testing,combine all units check interactions among all those units which is called " Integration Testing ".

      - Based on the availability of the source code,the integration testing will be carried out in four approaches..

1.Top-down Approach

2.Bottom-up Approach

3.Hybrid Approach

4.Big-bang Approach

Explaining about Software testing and Components?

- Software Testing is a process of test an application/project with the intention of finding defects.

- Software Testing means combination of Verification and Validation.

              " Software testing= Verification + Validation "

1.Verification:

                       - It is a process of verify developing  project is right or not.

                       - It is also called as " Static Testing ".

                       - It is to check whether s/w conforms the specifications and it is done by management people and technical people and developers.

2.Validation:

                       - It is a process of validating the developed project is right or not.

                       - It is also called " Dynamic Testing ".

                       - Verification is the process of checking the project is right or not.but validation is to check whether the software meets the customer expectation.this is done by test engineers(Quality Analyst's) and Client-side people.

1.Static testing:

               - It's a process of verifying that developing product is right or not.It is also called as "Module Testing or Component testing".

               - It will be carried out with the help of Reviews and Walk-through's. 

Static Testing 
             - Reviews
                        1.management Review
                        2.Technical Review
                        3.Code Review
                        4.Formal Review
                        5.Informal Review

              - Walk Through's

2.Dynamic Testing:

               - It is process of validating the developer's system is right or not.It is also called as "clear-box testing or structural testing".

                   - It will be carried out with the help of White-Box Testing and Black-Box Testing.

Dynamic Testing
           - Unit Testing
           - Integration Testing
           - System Testing
           - User Acceptance Testing.
Note:
1. White-box Testing = Unit Testing + Integration Testing.
2. Black-box Testing = System testing + User Acceptance Testing.

                                                                                                    

Brief Information about Software Developement Lifecycle(SDLC) Models?

- There are various software development approaches define and design which are used during development process of software.

- Those approaches are also referred as software development process models.

- SDLC models are 2 types.They are:

           1.Sequential Model

           2.Incremental Model

1.Sequential model:

           - Those models are best suitable for small size projects,where all SDLC activities will be carried out one after another for the entire project.

           - These model consists of two models.They are

                                     1.Waterfall model

                                     2.V model

2.Incremental Model:

           - Those models are besst suitable for big-size projects.

           - This model consists of 5 models.They are

                                     1.RAD Model

                                     2.Fish Model

                                     3.Prototype Model

                                     4.Spiral Model

                                     5.Agile Model