Method 3: - Perform cosmetics functions
2. Large Scale Organization: -
High Priority +
High Severity Negotiation between Tester & Developer.
2. Large Scale Organization:
-`
High Priority +
High Severity
Communication between Tester & Developer
Note: - As per the above process tester are not suppose to report the defects directly to the development team. The defects should be reviewed QA Lead, QA Manager and should get approval.
QA Lead Team Lead
QA Engineering Developer
Project Manager
Client
QA Manager
Product Manager
Project Manager
QA Lead
QA Engineering
Team Lead
Developer Client
Defect Status / Bug Life Cycle:
Accept Reject
If it is Failed
Retest By QA Team Developer Pass
Resolution Types: - When a tester are reports to the developer he will executed the same test case in this system and pass some resolutions type to QA Team.
1.
Duplicate: - Developer reject defect due to already existing of the defect.
2.
Enchantment: - Reject defect due to not belong to current version, we should targeted for up coming version.
3.
Not Applicable: - Developer is not accept & reject but he required more information about issues.
4.
Function as Design: - Working as our test case designee so developer is rejecting.
5.
Not Reproducible: - Developer is not accepting & rejects the defect, but he required more strong reasons to work on that issues.
6.
Fix: - Accepted for resolving.
7.
Software & Hardware limitation: - Developer reject defect due to defect is related to S/W & H/W.
8.
Miss Understanding: -Developer is not accepting & reject but requesting QA Team to Understand.
New Defect
Report Defect
Open
Re-Open Resolve
d
In-Progress
Assigne d
Submitt ed
Fixed Enchant Deferred
ment Duplicat
e
Close
Bug Life Cycle:
QA Team
Developer
QA Team Types Of Bugs:
-1. User Interface Bugs (Low Severity).
• Understandable of Screens (High Severity).
• Spell Checks (High Severity).
2. Input Domain Bugs (High Severity).
3. Calculation Bugs (High Severity).
4. Security Bugs (High Severity).
5. Database Bugs (High Severity).
6. Load Condition Bugs (High Severity).
7. Hardware & Software Bugs (Medium Severity).
8. Race Condition Bugs (High Severity).
9. Build Version Controls (High Severity).
10. Identification Controls (Low Severity).
11. Functional Bugs (High Severity).
(X) Test Closer:
After completion of the entire functional testing on the current project, QA Lead will concentrate to develop finial review document in order to submit to the Management and develop the documentation which is called as Final Test Summary Report (FTSR). This is the part in Software Releasing Notes (SWRN)
To develop Software Release Notes (SWRN) to above document are required to finalize.
Detected the Defect
Report the Defect
Re-Producible the Defect (Y/N)
Fix the Bug
Resolve the Bug
Close the Bug
Test Initiation Test Plan Test Design
Test Case Reviews (CRTM / VTM) Test Execution
Defect Reporting Test Logs
Test Summary Reports Finally Test
Summary Report (FTSR)
The Software Release Notes (SWRN) document consist of 1. Purpose.
2. Features.
3. Functionality that are completed.
4. System Requirement.
5. Bugs Closed.
6. Known Issues / Bugs.
7. Release Mode / Medium.
What is the Testing Process we are following in our organization? (Interview Question)
QA Team
Sign In: - It is a process which is followed by the Management in order to setup agreement between company management & client. It defines to monitors and measure the total strength devolvement team process as well as testing process in order to maintain good relationship between client & company management.
Information Gathering: - This is the first step and very crucial step to collecting all information regarding to the developed project or application. This is done by the BRS peoples.
In Every Company followed the V-Model to maintain the better quality.
V-Model: - It is a mapping between various development stages and testing stages. V – Stands for
“Verification & Validation”. It can be followed by large scale organization as it is expensive model. But where as small scales will follows Functional & System Testing as mandatory. Because it is a bottleneck phase.
Stage (1): Test
It is the first process that should be followed by very organization in order to gather client business requirement. That contains of BRS.
This document can also be called “User Requirement Specification” (URS) or “Client / Customer Requirement Specification” (CRS) or “Business Requirement Document” (BRD) or “Functional Requirement Specification” (FRS).
It is a company level document as well as project level document which should be developing for the entire development team & tester team. This document defines approaches, guidelines, project planning, schedules and tasks that should be followed for the current project.
Identify the Type of the Project:
Here the QA Manager or Project Manger will involved identifying the type of the project and it will concentrate to the next step.
Software Requirement Specification (SRS) / Use case Document (UCD): - After completion of developing of BRS document business analysis people will concentrate to developed a SRS document basing on BRS document. This document defines customer use cases, requirements and system requirements to be developed on new software. The contents of SRS document are
Test
• Use case Diagrams.
• Use cases.
• Task flow Diagrams.
• Pictorial Diagrams (optionally).
• Actors.
• Preconditions.
• Post conditions, etc.
After completion of developing SRS documents it will be send to customer / client to get approval.
NOTE: - A tester will develop test cases basing on this SRS information.
Design: - After completion of information gathering and developing a software design category people will concentrate to design architecture the application. In real times to get approval from client side they will be designing markup design basing on SRS document.
After getting approval from client side they will enter in to detailed design to develop database front-end from objects like textbox, list box, checkbox, radio button, etc., To design a software they follow the below two process
• High Level Design (HLD).
• Low Level Design (LLD).
•
High Level Design (HLD):-High Level Design document define the overall hierarchy of all functionalities from leaf module to root module.
•
Low Level Design (LLD): -Low Level Design document defines the “Internal process of every sub modules” that are available in one application. It is also called as an “Internal Logics”.
Coding: - After completion of design software a programmer will concentrate to physically construct software. This also called as “Implementation”. A programmer will follow different technical techniques to code software. The most commonly followed languages for any software development C, C++, Java, Dot Net, etc. after completion of coding a software a programmer will follow some white box testing (WBT) technique to verify logical errors, syntax errors, loop termination, etc.
White Box Testing:
Unit Testing: - (Here Tester not involved only developers)
It is the first technique which is followed by developer after coding software during this process a programmer wills constructs to encounter errors, fault, and failures in a written coding.
Black Box Testing:
-After completion of entire development team process a tester will receive initial Build from a development team, where tester can download by using FTP (File Transport Protocol) or IP (Internet Protocol).
Smoke Testing:
-Before going for either Manual or Automation testing a tester have to verify the initial build whether it is a stable or un-stable. If it is stable tester will accept, if it is un-stable tester will reject and give strong reason to the development teams which is called as “Smoke Testing”.
Black Box Testing (BBT) is again divided in to the below 4 Techniques.
1. Usesibility Testing.
2. Functional Testing.
3. Performance Testing.
4. Security Testing.
Identify the Current Requirements:
-To develop project level document project manager will follow various types of steps as shown below.
Step (1): - Project Manager to requite resources for the current project testing.
Step (2): - Project Manager to go through QA documentation to under stand the approaches we follow.
Step (3): - Project manager to identify the type of the project that is received to our organization.
Step (4): - Project Manager have to determine current project requirements which are necessary for our current project testing.
Step (5): - Project Manager identify the feature requirements of the current projects testing, so Project Manager will add some of the factors which are required in feature for the current projects.
Step (6): - Project manager has to identify the tactical risks that are involved in the selected TRM Columns, so Project manager dependent upon risks Project Manager will delete some of the Factors from the TRM table and finalize the factors for the entire project testing.
After Finalizing TRM columns Project Manager has to develop Project planning for the entire year by given schedules, tasks, approaches for the entire project.
Identify the Tactical Risks: -
Risks: Risk is a problem that we are facing in organization like lack of time, lack of budget, lack of Resources, lack of preparation documentations, delays and delivery of build, etc.
Mitigation: To over came the above problems QA Manager will go other alternate things methods to achieve objectives.
Approach the Entire Team: -
Here the QA Manger / QA Lead will assign the Roles & Responsibility. Roles are “Designations” of the employee and Responsibility takes an each roles.
Stage (2): Test Plan: - (By QA Lead)
After a compilation of both company & project level documents QA Lead will concentrate to develop test plan document IEEE format. To develop test plan document QA Lead have to go through various types of document in order to develop a very good test plan.
After completion testing team formation and identifying risks QA Lead will concentrates to develop a test plan document for the entire formed QA Team. This document defines approach, roles & responsibilities, time duration of the project and environment to be used. And also explain
• Who to test?
• What to test? To develop the beside test plan some companies follows IEEE format.
• When to test?
• How to test?
They follow the entire 16 steps to prepare the test plan for the current version.
Stage (3): Test Design ( Prepare the Test cases ): -
This is the major part involves of the tester for design test cases in the real times. A tester can develop test case for any application like
• New Request.
• Enhancement.
• Defects.
• User Accepting Test (UAT).
Before going for test cases a tester have under gone some training in order to capture them entire customer business requirements as per the test plan. The document tester follows to design testing cases.
1. SRS / FS / Requirement Document / Use case Document / Technical document / Design Document 2. Test plan document and some time will follow test strategy documents.
To develop test cases, the tester will follow below three methods.
Methods:
1. Business Requirement Based Test case design.
2. Input Domain Based test case design.
3. User Interface (UI) Based test case design.
Method 1: - BRS SRS Use Case Test Cases.
Method 2:- BRS Design Document Data Models (ER Models) Test Cases.
Method 3: - Perform cosmetics functions.
Stage (3.1): RTM (or)
After completion of developing Test cases for the current version of all functionality QA Lead or QA Manager will concentrated to review all the test cases for the completeness & correctness, and develop a documentation called as Requirement Traceable Matrixes (RTM) or Validation Traceable Matrixes (VTM).
This document defines mapping between the developer test case and the customer requirements.
Review documents developed by QA Leas or QA Manager in order to maintain completeness & correctness of all test cases. And they will decide what the test cases to be done under Manual are & what are the test cases to be done under Automation. This is the finalized document for entire application testing.
Stage (4): Test Execution:
After completion of entire development team process a tester will receive initial build from development team and once they complete installing successfully they can test the applications in two types there are 1. Manual Testing. 2. Automation Testing.
After completion of entire development team process deployment team will concentrate to deploy the current version build into soft base in server with respected to supported software’s.
A tester will download the current version through FTP / IP in to they system and they installed the current version according to the initialization guide line by the development team. To maintain all
types of version like, New, Old & Modified build are versions they may use configuration management tools like Visual Source Safe (VSS) & Congruent Version System (CVS) or Quality Center 10.
A developer will mail to testing team regarding URL to work with local system, IP address to work with remote system and also initializations instructions if required.
To executed the application a tester will follow the below Levels
Level – 0: - This is the first process which should be following for every version testing in order to verify the stability of the application. This can be followed both Manual Testing & Automation Testing. During this process a tester have to verify the basic functionality like checking every menu link & entire some valid or invalid data, to check whether accepting or not etc. A tester will follow the below 8 factors (Octangle Factors) are:
1. Understandable 2. Maintainable 3. Operate able 4. Controllable 5. Simplicity 6. Consistency 7. Testable 8. Automoble
The above 7 factors are followed for Manual Testing Process and 8th Factor is Automation Testing.
If any one of the factor is failure tester can reject the initial build.
Level – 1: - After complete of all possible Smoke/Sanity testing testers will concentrate to execute the entire functionality test cases like Basic Functionality (P0), General Functionality (P1) and Cosmetic Functionality (P2). During test execution, a tester has to compare the given expected results with application behavior values in step by step and they need to maintain documentation is called as
“Test Logs”.
Test Logs: - 1. Passed 2. Failed
3. Not Completed 4. No Run
5. Deferred 6. Blocked.
During execution, if tester is finding any mismatches they need to reports Log CR’s (Change Request) in to defect tracking tool
Level – 2: - Regression Testing.
Level – 3: - This level of testing is followed on the Master Build or High Bug density
•
Master Build: - The product / application which is readiness to release the customer or the product / application which is totally free from bugs.•
High Bug density: - The average number of bugs found in a modules.This level testing is following once again to on Master build to ensure bug fix works & accuracy of any side effects.
Stage (4.1) Test Reporting:
-During Level – 1 execution if tester are finding any defects or mismatches they need to log those issues into a defect tracking tool like Quality Center (QC) & Clear Quest or Bugzilla etc., are some time a tester can report through Excel sheet format. To report the defects a tester may follows IEEE format in order to maintain better planning for the entire test cases.
Stage (5) Test Close:
After completion of the entire functional testing on the current project, QA Lead will concentrate to develop finial review document in order to submit to the Management and Develop the documentation which is called as Final Test Summary Report (FTSR). This is the part in Software Releasing Notes (SWRN) User Accepting Testing (UAT):
-After completion of entire functional testing on one application or product management team will concentrate to collected feedback from the real customers and real like customer. In this process we followed two type of testing that are Alpha (
α
) Testing and Beta (β
) Testing.In general every client will release Beta (
β
) version to the customers in order to collect feedback, in real time senariours a tester have to conduct live testing on Beta (β
) version in front of the customer.Maintains Document: -
After completion of successful User Accepting Test(UAT) process a tester have to a maintained all type of documents for feature references, if any customer suddenly request
Sing Off: - After completion of entire reviews & UAT Project Manager will concentrate to Signed Off the Product / Application to the customer, which is called Shipment.