Difference between Quality analyst and Quality Controller..?

Here we discuss about quality analyst and quality controller.

Quality Analyst:

             A set of activities designed to ensure that the development and maintenance process to ensure system can meets objectives and requirements.

Quality Controller:

            A set of activities designed to evaluate to developed worth product.

Explaining about Test Engineers Responsibilities..?

Here we discussing about test engineer responsibilities.

They are

1.Analyse requirements

2.Involved in preparing the test plan

3.Involved or prepared test scenarios and test case modules.

4.Prepare test data for test cases

5.Preparing test environment to execute test cases

6.Analyse test cases prepared by team members

7.Executing test cases and preparing defect report.

8.Giving mandatory information of a defect to modify a defect.

9.Attending daily meetings and preparing daily reports.

10.After completion of defect reports,suggestion document to improve the quality of the application.

11.Communication with test lead and senior tester's and customers.

12.Conducting review meeting the team and

13.Involved in prepare test summary reports.

Explaining briefly about Test Execution in S/W Testing Life Cycle..?

Test Execution:

- After completion of test design,Tester concentrating on test execution.

- At this stage,we need to compare expected value,actual value are equal or not.

- Executing a formal meeting,Formal test/informal test cases to conform the business requirements and To identify the defects is called " Test Execution".

-While conducting test execution,tester can follow below approaches:

1.Formal meeting

2.Configuration Repository

3.Establish Test Environment

4.Test Execution Levels.

Explaining about Test Cases and Types?

Test Cases:

 - Test case is a set of pre-conditions,test scripts,input data and expected result to validate functionality of system.

OR

 - Test case is a brief description of what to test and how to test in application.

Types of Test-Cases:

 1.Positive Test-case:

    - If test case is prepared to check what system supports to do,then it's called positive test case.

ex: Check login with valid inputs.

 2.Negative Test-case:

    - If test case is prepared to check what system not supports to do then it's called negative test case.

ex: check login with invalid inputs.

- while preparing test-cases,Every tester can follow IEEE A29 format.

Explaining about Test Scenario's..?

Test Scenario:

  - An Item/Functionality to be tested in the application is called Test Scenario.

  - what to test is called " Test scenario ".

Example:

 Teset scenario's for Gmail application:

   - verify login functionality of Gmail application login page.

   - verify need help functionality of gmail application login page.

   - verify create an account functionality of gmail application login page.

   - verify listbox functionality of gmail application login page.

   - verify links functionality of gmail application login page.

Example of Test scenario prepared for bank application: 

 

Explaning about Non-Functional System Testing and these types?

Here,we are discussing about non-functional system testing and these types.
- After completion of functional system,test engineers concentrating on non-functional of the application.
- while conducting non-functional testing,we should concentrating on expectations of customers like
   1.GUI Testing
   2.Usability Testing
   3.Comparability Testing
   4.Hardware Configurable Testing
   5.Performance Testing
           - Load testing
           - Stress testing
           - Spike testing
           - Endurance testing
   6.Inter System Testing
   7.Installation Testing
   8.Recovery Testing
   9.Complex Testing
 10.Security Testing
           - Authentication/Authorization testing
           - Access control testing
           - Encryption/decryption testing

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

Exaplining about Testing Levels and Methods?

• Testing is the processing to test an application with an intention of finding defects or errors.
• In Testing,Four levels are available.

         They are :     1.Unit Testing

                          2.Integration Testing

                          3.System Testing

                          4.User Acceptance Testing

Note: 

  A. Unit Testing and Integration Testing combination is called "White-box Testing" & White-box testing means test the program by programmer,not the application.

  B. Collection of System Testing and User Acceptance Testing is called " Block-box Testing" & Block-box Testing means test an application by Quality Analyst/Client,not the program.

• In Testing, 2 methods are available.They are

                  1.White-Box Testing

                  2.Block-Box Testing

Explaining about Software Development Life cycle(SDLC)?

Today Iam discuss about SDLC.

- SDLC stands for Software Development Life Cycle.

- Without SDLC,there is no Software Project.

- Project means which is developed for specific client requirement.

- In real-time process,

      - In the IT company,projects comes to the company by CEO from clients.CEO(Chief Executive Officer) communicate with the clients to get a projects.

      - Once Project is assigned/conformed to specific company ,CEO arrange the meeting with Project managers and discussing about the project and assign that project to one specific Project manager.

                                           Before starts SDLC process,above 2 steps are done to the every project.

                         

  1st Step:

        Initialize the project and prepare a project initial note by Project manager.

 2nd Step:

        Specific requirements gathering from Clients by Business Analyst(B.A) and B.A prepares 2 documents like Business Requirement Specification(BRS) and System Requirement Specification(SRS) for understanding the project easily.

Definition of Testing and Different Types of Testing?

Hai friends...Today I share the information about "Testing tools".

Now a days Everyone calls Name as "Testing Tools".but In IT sector,we should call "Software Testing" is the actual name of  Testing Tools.

Definition of Testing:

           It's a process of to test an application with an intention of finding defects.

-->Testing is dividing into 2 types.They are:

1.Manual Testing

2.Automation Testing

1.Manual Testing:

    It's a process to test an application by giving input's and by observing output's manually is called Manual Testing.

2.Automation Testing:

     - It's a process to test an application with the help of tolls and software's i.e called Automation testing.

     - In Automation testing,Different types of tools are available.

         They are :  A) Quick Test Professional(QTP)[ HP company licensed tool]

                        B) Selenium(Open Source)

                        C) Load Runner

                             

Real-Time 3-Tier architecture Application Example using ASP.NET

In 3-Tier programming architecture, the application development is broken into three main parts.
These are:
1.Application/Presentation layer
2.Business Acess Layer(BAL) and
3.Data Access Layer(DAL).
These separations ensure independent development of those layers such that a change in one does not affect the other layers. For instance a change in the logic of the DAL layer does not affect the the BAL nor the presentation layer. It also makes testing easier in that a whole layer can be replaced with a stub object.

For example instead of testing the whole application with an actual connection to database, the DAL can be replaced with a stub DAL for testing purposes. The DAL deals with actual database operations. These operations are inserting, updating, deleting and viewing. The BAL deals with the business logic for a particular operation. The PL has the user controls for interacting with the application.

3-Tier programming architecture also enables re-use of code and provides a better way for multiple developers to work on the same project simultaneously.
1.Start a new website project
2.Design you page as shown below,
                           

3.Add sub-folders and class objects within the App_code folder as shown below,
                       

 /*
    1.First Add sub-folders and class objects within the App_code folder and then
     Create Database(RegDB.mdf) and create a table (Registration) with field names as shown below(regBEL.cs file).