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