What is difference between Retesting and Regression Testing?
Retesting: It is conformation testing after a defect is fixed, developers will send that to testers as status changed to RPSIT. Then once again we will go for “retest” that test case for confirming the original defect has been successfully removed.
Regression Testing: Testing which ensures that existing build functionality remains same even a new build is released.
In Real Time: Suppose a version 2.1 is existing and a new requirement comes say 2.2 and this 2.2 works properly with existing 2.1 functionality.
20 October 2010
12 October 2010
What is CRM?
CRM Stands for “Customer Relationship Management“. CRM is a Process or Methodology used to learn more about customers needs and behaviors in order to develop stronger relationships with them.
It will help together lots of Pieces of information about Customer, Sales, Marketing effectiveness, and responsiveness and Market trends.CRM is the Business Strategy that aims to Understand, Anticipate, and Manage and personalize the needs of an Organizations Current and Potential Customer.
It will help together lots of Pieces of information about Customer, Sales, Marketing effectiveness, and responsiveness and Market trends.CRM is the Business Strategy that aims to Understand, Anticipate, and Manage and personalize the needs of an Organizations Current and Potential Customer.
About Siebel CRM
Siebel is a brand name of Oracle Corporation. Siebel System Inc., founded by Thomas Siebel in 1993, was principally engaged in the design, Development, Marketing and support of CRM applications. On September 12, 2005 Oracle Corporation had agreed to buy Siebel System for $5.8 billion.
Major Releases:
Oracle Siebel 8.0
Oracle Siebel 7.8
Siebel 7.7
Siebel 7.5
Siebel 7.0
Siebel 6 (also known as Siebel 2000)
Siebel 99
Siebel 98
Siebel system is the worlds leading provider of “Customer Relation Management " software solutions and a leading provider of software applications for business intelligence and standard-based integration. Siebel provide CRM software solutions for any kind of organization, any type of business and any type of budget.
Major Releases:
Oracle Siebel 8.0
Oracle Siebel 7.8
Siebel 7.7
Siebel 7.5
Siebel 7.0
Siebel 6 (also known as Siebel 2000)
Siebel 99
Siebel 98
Siebel system is the worlds leading provider of “Customer Relation Management " software solutions and a leading provider of software applications for business intelligence and standard-based integration. Siebel provide CRM software solutions for any kind of organization, any type of business and any type of budget.
11 October 2010
Priority & Severity
Priority: How important to fix the bug & it will be change according to situation.
P1- High-- No work around is possible. (Menu- New if not possible , need to fix immediately)
P2- Medium-- Before release we need to fix, work around is possible.
P3- Low-- If we have time, it will fix, otherwise it should move to deferred status.
Severity: How bad the bug is and impacts all the application. (OR) How serious the defect.
S1- Critical-- System crash (Data loss)
S2- Major-- Wrong result, loss of functionality (Like in calculator missing +, _, *, %,..)
S3- Medium-- Miss Spelled
S4- Minor
P1- High-- No work around is possible. (Menu- New if not possible , need to fix immediately)
P2- Medium-- Before release we need to fix, work around is possible.
P3- Low-- If we have time, it will fix, otherwise it should move to deferred status.
Severity: How bad the bug is and impacts all the application. (OR) How serious the defect.
S1- Critical-- System crash (Data loss)
S2- Major-- Wrong result, loss of functionality (Like in calculator missing +, _, *, %,..)
S3- Medium-- Miss Spelled
S4- Minor
03 October 2010
V- Model
Explain the process of V-Model?
Main theme of V-Model is Verification and Validation.
Verification represents “Are we building the product RIGHT?" i.e. Verification is a process to verify the software product or application is developed the right way.
Validation is a process of finding out if the product being built is right? i.e. whatever the software product is being developed, it should do what the user expects it to do.
All types of testing methods are basically carried out during the Validation process. Test plan, test suits and test cases are developed, which are used during the various phases of Validation process.
Requirement & Gap Analysis:
- Business analyst (BA)gathers the requirements from Client and prepares Business Requirement Document (BRD)
- User Acceptance Testers (UAT) go through the same BRD and Prepares UAT test case design/Checklist & UAT test plan document
System Design & Planning:
- SA review and go through the BRD and prepares SRS document
- System testers review and go through the SRS and prepare System test case
design & test plan documents
Architect & Module Design:
- Senior developers review and go through the SRS and prepares the HLD & LLDs
- Development team review and go through the HLD and LLDs then prepare the integration & Unit Test case design and test plan documents
Coding:
Once the Coding is done same programming team would validate the developed system code by performing the Unit, Integration testing based Unit & Integration test case design and plan.
System Testing: Testers validate the developed system by executing the design test cases against the application as per test plan
UAT testing: After System testing, UAT testers validate the developed application based UAT test case design & test plan.
V-Model Advantages:
1. An important aspect of this model is that testing activities like planning, test designing
happens well before coding
2. Its more flexible compare to Waterfall model
V-Model disadvantages:
1. It needs lot of resources and money.
2. it needs an established process to implement
3. It can be implemented by only some big companies
Main theme of V-Model is Verification and Validation.
Verification represents “Are we building the product RIGHT?" i.e. Verification is a process to verify the software product or application is developed the right way.
Validation is a process of finding out if the product being built is right? i.e. whatever the software product is being developed, it should do what the user expects it to do.
All types of testing methods are basically carried out during the Validation process. Test plan, test suits and test cases are developed, which are used during the various phases of Validation process.
Requirement & Gap Analysis:
- Business analyst (BA)gathers the requirements from Client and prepares Business Requirement Document (BRD)
- User Acceptance Testers (UAT) go through the same BRD and Prepares UAT test case design/Checklist & UAT test plan document
System Design & Planning:
- SA review and go through the BRD and prepares SRS document
- System testers review and go through the SRS and prepare System test case
design & test plan documents
Architect & Module Design:
- Senior developers review and go through the SRS and prepares the HLD & LLDs
- Development team review and go through the HLD and LLDs then prepare the integration & Unit Test case design and test plan documents
Coding:
Once the Coding is done same programming team would validate the developed system code by performing the Unit, Integration testing based Unit & Integration test case design and plan.
System Testing: Testers validate the developed system by executing the design test cases against the application as per test plan
UAT testing: After System testing, UAT testers validate the developed application based UAT test case design & test plan.
V-Model Advantages:
1. An important aspect of this model is that testing activities like planning, test designing
happens well before coding
2. Its more flexible compare to Waterfall model
V-Model disadvantages:
1. It needs lot of resources and money.
2. it needs an established process to implement
3. It can be implemented by only some big companies
Waterfall Model
Explain the process of Waterfall Model?
The waterfall model is a sequential software development process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Requirements, Design & Planning, Coding, Testing and Maintenance.
In this model each phase has a well defined starting and ending point, with identifiable deliveries to the next phase
The outputs from a specific stage serve as the initial inputs for the following stage.
Advantages (Pros):
In this model there would be proper design documentation
Well defined tasks and deliverables
This will be useful for large complex projects
Disadvantages (Cons):
Each phase should be completed before starting the next phase; it’s difficult to go back to the earlier phase if any problem is occurred.
Till the build is given for testing, the testers will be Idle. Hence man power is wasted.
The waterfall model is a sequential software development process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Requirements, Design & Planning, Coding, Testing and Maintenance.
In this model each phase has a well defined starting and ending point, with identifiable deliveries to the next phase
The outputs from a specific stage serve as the initial inputs for the following stage.
Advantages (Pros):
In this model there would be proper design documentation
Well defined tasks and deliverables
This will be useful for large complex projects
Disadvantages (Cons):
Each phase should be completed before starting the next phase; it’s difficult to go back to the earlier phase if any problem is occurred.
Till the build is given for testing, the testers will be Idle. Hence man power is wasted.
02 October 2010
System Testing
What is System testing?
The process of performing a variety of tests on a system to explore functionality or to identify problems.
In this three types of testing levels are there.
Usability Testing
Functional Testing
Non-Functional Testing
a. Usability testing/User Interface testing (UIT): The testing team validating the user friendliness of the application like
Easy to use : Verifying that application screen are understandable to layman level
Look and feel : Verifying that application screens are attractable
Speed interface: verifying that the application is having short navigations to complete the tasks.
Verifying the spelling of each word in every screen
Verifying the background color of each screen
Verifying the borders of each and every section available in the application screens
Verifying the object alignment in every screen
Verifying the line spacing uniform between all the objects through the screens
b. Functionality testing: In this phase testers are validating the developed application functionality against SRS document(It is a block box technique)
Validating the application behavior against SRS doc
Input & output validation ( Taking correct type and size i/ps and providing correct o/ps)
Backend updating coverage (The impact of front end screen operations on data tables content)
c. Non functionality testing:
Reliability / durability: measures the application stability under load and continuation usage
Compatibility/Portability: Validating the application functionality in customer expected platforms like different browser & Operating systems
Ex1: Performing the system testing in IE, Mozilla Firefox, Opera, Google Chrome, etc is called Browser compatibility testing
Ex2: Performing the system testing in Windows XP, Vista, W7, and Mac etc is called Operating System compatibility testing
Configuration testing : Validating the application functionality in customer expected hardware platforms like different hard ware’s & Networks
Ex: Technology networks, Topology Networks, Printers, high end & Low configuration systems (like 32 bits, 64 bits, RAM levels, Processor levels, etc)
Internationalization testing: Validating the developed soft ware with multi language characters
Patch installation testing: Once any patches installed in to application servers from Microsoft updates and Norton’s security updates testers would perform the smoke level of application testing
Performance testing: Validating the developed application under different levels of load and configuration
Note1: Performance testing the part of non functionality testing which would be tested by the separate performance testing team
Note2: Load, Stress, Endurance, Data volume testing are comes under part of performance testing
Load Testing: Performing the application testing under customer expected configuration & load
Note: Load/ Scale means that no: of concurrent users are accessing the that software
Stress testing: Performing the application testing under customer expected configuration and peak load to breaking point of load
Endurance /Soak testing: Performing the application testing under customer expected configuration and multiple levels of load to determine if the application can sustain the continuous expected load
The process of performing a variety of tests on a system to explore functionality or to identify problems.
In this three types of testing levels are there.
Usability Testing
Functional Testing
Non-Functional Testing
a. Usability testing/User Interface testing (UIT): The testing team validating the user friendliness of the application like
Easy to use : Verifying that application screen are understandable to layman level
Look and feel : Verifying that application screens are attractable
Speed interface: verifying that the application is having short navigations to complete the tasks.
Verifying the spelling of each word in every screen
Verifying the background color of each screen
Verifying the borders of each and every section available in the application screens
Verifying the object alignment in every screen
Verifying the line spacing uniform between all the objects through the screens
b. Functionality testing: In this phase testers are validating the developed application functionality against SRS document(It is a block box technique)
Validating the application behavior against SRS doc
Input & output validation ( Taking correct type and size i/ps and providing correct o/ps)
Backend updating coverage (The impact of front end screen operations on data tables content)
c. Non functionality testing:
Reliability / durability: measures the application stability under load and continuation usage
Compatibility/Portability: Validating the application functionality in customer expected platforms like different browser & Operating systems
Ex1: Performing the system testing in IE, Mozilla Firefox, Opera, Google Chrome, etc is called Browser compatibility testing
Ex2: Performing the system testing in Windows XP, Vista, W7, and Mac etc is called Operating System compatibility testing
Configuration testing : Validating the application functionality in customer expected hardware platforms like different hard ware’s & Networks
Ex: Technology networks, Topology Networks, Printers, high end & Low configuration systems (like 32 bits, 64 bits, RAM levels, Processor levels, etc)
Internationalization testing: Validating the developed soft ware with multi language characters
Patch installation testing: Once any patches installed in to application servers from Microsoft updates and Norton’s security updates testers would perform the smoke level of application testing
Performance testing: Validating the developed application under different levels of load and configuration
Note1: Performance testing the part of non functionality testing which would be tested by the separate performance testing team
Note2: Load, Stress, Endurance, Data volume testing are comes under part of performance testing
Load Testing: Performing the application testing under customer expected configuration & load
Note: Load/ Scale means that no: of concurrent users are accessing the that software
Stress testing: Performing the application testing under customer expected configuration and peak load to breaking point of load
Endurance /Soak testing: Performing the application testing under customer expected configuration and multiple levels of load to determine if the application can sustain the continuous expected load
Unit Testing
What is Unit Testing or White Box Testing?
White Box testing means while the developer developing the code, they are testing the code of an application with different techniques.
White Box Testing using these techniques
Basic path coverage => whether the corresponding program is running/not without having runtime errors.
Control structure coverage=> verifies the correctness of taking i/ps and providing o/ps of that program.
Program technique coverage => to calculate the execution time of a program.
Mutation coverage=> verifying that whether our program correctly and completely tested/not.
White Box testing means while the developer developing the code, they are testing the code of an application with different techniques.
White Box Testing using these techniques
Basic path coverage => whether the corresponding program is running/not without having runtime errors.
Control structure coverage=> verifies the correctness of taking i/ps and providing o/ps of that program.
Program technique coverage => to calculate the execution time of a program.
Mutation coverage=> verifying that whether our program correctly and completely tested/not.
Defect Life Cycle
What is defect life cycle?
While the tester logs the defect, he set the status of defect as new and assigns it to dev. Then developer will open and fix it, after change the defect status as RPSIT. After SIT build complete, Build master change defect status as RTV and assign to tester. Then tester will test it, if defect pass it will close otherwise it will be reopen and again assign to dev.
Duplicate? - When two bugs are same, which one is log first that is in open, another one is in duplicate status.
Deferred? - Which bugs are not affected by other functionality, these bugs are set in deferred status
Cancelled?
Rejected? - If the developer feels that the bug is not genuine (valid), he rejects the bug.
On hold? – Which bugs are depending on another bug, these bugs are set as “on hold”.
While the tester logs the defect, he set the status of defect as new and assigns it to dev. Then developer will open and fix it, after change the defect status as RPSIT. After SIT build complete, Build master change defect status as RTV and assign to tester. Then tester will test it, if defect pass it will close otherwise it will be reopen and again assign to dev.
Duplicate? - When two bugs are same, which one is log first that is in open, another one is in duplicate status.
Deferred? - Which bugs are not affected by other functionality, these bugs are set in deferred status
Cancelled?
Rejected? - If the developer feels that the bug is not genuine (valid), he rejects the bug.
On hold? – Which bugs are depending on another bug, these bugs are set as “on hold”.
Design Test Cases
How to design Test Cases?
First BA will conduct “walk through”, it represents the meeting with STG team, dev team and testing manager for explaining business requirements one by one. Any one can have queries, BA will clarify. After complete the walk through, peer review meeting on requirements. Then STG team will prepare the test cases based on the F.R.S and using ECP (Equalence Class Partition), BVA (Boundary Value Analysis) techniques. Once complete the preparation of test cases, STG will conduct internal buddy review on prepared TCs and getting approval from architect, designer and BA. Then approved test cases will upload in QC.
First BA will conduct “walk through”, it represents the meeting with STG team, dev team and testing manager for explaining business requirements one by one. Any one can have queries, BA will clarify. After complete the walk through, peer review meeting on requirements. Then STG team will prepare the test cases based on the F.R.S and using ECP (Equalence Class Partition), BVA (Boundary Value Analysis) techniques. Once complete the preparation of test cases, STG will conduct internal buddy review on prepared TCs and getting approval from architect, designer and BA. Then approved test cases will upload in QC.
Subscribe to:
Posts (Atom)