1. Test data(User Name, Password etc)
2. Type of testing:
* Load Testing
* Stress Testing
* Endurance Testing
3. Specific time that when the scripts can be executed.
4. Architecture of the application
5. Load Generator
6. Server configuration
7. Expected Delay Time.
8. Expected Throughput time.
9. Exact bandwidth.
10. How many users going to access the application?
11. How many concurrent users?
12. What are the roles of the users?
13. Type of the application.
14. What are all the protocols using?
15. How many peak users?
16. What type of scenarios facing?
17. How often the peaks and when they are occurring?
Saturday, January 31, 2009
Status in Loadrunner controller Scenario Groups
Scenario Groups pane in the Run view of controller is to monitor the actions of all the Vusers and Vuser groups in the scenario.
The Status field of each Vuser group displays the current state of each Vuser in the group
1. Down Status: Vuser is down
2. Pending: Vuser is ready to be initialized and waiting for an available load generator
3. Init: The Vuser is being initialized on the remote machine.
4. Ready : The Vuser already performed the init section of the script and is ready to run.
5. Running: The Vuser is running. The Vuser script is being executed on a load generator
6. Rendezvous: The Vuser has arrived at the rendezvous and is waiting to be released by LoadRunner.
7. Done.Passed : The Vuser has finished running. The script passed.
8. Done.Failed : The Vuser has finished running. The script failed.
9. Error: A problem occurred with the Vuser
10. Gradual Exiting : The Vuser is completing the iteration or action it is running Before exiting.
11. Exiting : The Vuser has finished running or has been stopped, and is now exiting.
12. Stopped The Vuser stopped when the Stop command was invoked.
Available Protocols in Loadrunner 8.0
1. Application Deployment Solution Protocol: Citrix protocol.
2. Client/Server Protocols : DB2 CLI, DNS, MS SQL, ODBC, Oracle (2-tier), Sybase Ctlib, Sybase Dblib, and Windows Sockets protocols.
3. Custom Protocols: C templates, Visual Basic templates, Java templates, Java script and VBscript type scripts
4. Distributed Components: For COM/DCOM, Corba-Java, and Rmi -Java
5. E-business protocols: For FTP, LDAP, Palm, Web (HTTP/HTML), Web Services, Dual Web/Winsocket protocols.
6. Enterprise Java Beans Protocols: EJB Testing and Rmi-Java protocols.
7. ERP/CRM protocols: For Baan, Oracle NCA, People soft-Tuxedo, People soft 8,
8. SAPGUI, SAP protocols -Web, and Siebel (Siebel-DB2CLI, Siebel-MSSQL, Siebel-Web, and Siebel-Oracle) protocols.
9. Legacy protocols: For Terminal Emulation (RTE).
10. Mailing Services protocols: Internet Messaging (IMAP), MS Exchange (MAPI),
POP3, and SMTP.
11. Middleware protocols: Jacada and Tuxedo (6, 7) protocols.
12. Streaming Protocols: For Media Player and RealPlayer protocols.
13. Wireless Protocols: For i-Mode, VoiceXML, and WAP protocols.
2. Client/Server Protocols : DB2 CLI, DNS, MS SQL, ODBC, Oracle (2-tier), Sybase Ctlib, Sybase Dblib, and Windows Sockets protocols.
3. Custom Protocols: C templates, Visual Basic templates, Java templates, Java script and VBscript type scripts
4. Distributed Components: For COM/DCOM, Corba-Java, and Rmi -Java
5. E-business protocols: For FTP, LDAP, Palm, Web (HTTP/HTML), Web Services, Dual Web/Winsocket protocols.
6. Enterprise Java Beans Protocols: EJB Testing and Rmi-Java protocols.
7. ERP/CRM protocols: For Baan, Oracle NCA, People soft-Tuxedo, People soft 8,
8. SAPGUI, SAP protocols -Web, and Siebel (Siebel-DB2CLI, Siebel-MSSQL, Siebel-Web, and Siebel-Oracle) protocols.
9. Legacy protocols: For Terminal Emulation (RTE).
10. Mailing Services protocols: Internet Messaging (IMAP), MS Exchange (MAPI),
POP3, and SMTP.
11. Middleware protocols: Jacada and Tuxedo (6, 7) protocols.
12. Streaming Protocols: For Media Player and RealPlayer protocols.
13. Wireless Protocols: For i-Mode, VoiceXML, and WAP protocols.
Friday, January 30, 2009
How to apply for CSTE exam
Examinations in India, China, Sri Lanka and Brazil are administered every 2
months (6 times a year) at Software Certifications Sponsored Test locations
and are written examinations.
Registration Process
Step 1:Register on the 'Customer Portal' section on
www.softwarecertifications.org
Step 2:Apply for Candidacy once you are logged in. You will have to enter
your Personal Info, Education, References, etc. in order to satisfy the
Candidacy Prerequisite checks. The Candidacy Payment Wizard will take you
through the payment process.
Step 3: You can Schedule an Examination when you feel ready to actually take
the Examination.
In order to take the written examination at these locations, you need to
register 30 days before the selected examination date by filling the form in
the 'Customer Portal' section on www.softwarecertifications.org and making
the required payment.
The eligibility criteria is available on
http://www.softwarecertifications.org
Payment Details:
CSQA & CSTE:
Option 1: US$350
[Application Fee+ Study Guide]
Option 2: US$420
[Application Fee + Study Guide + hard copy of the Study Guide]
CSPM: US$400
[Application Fee]
Mode: The fee (in US$ only) can be paid by a dollar draft/check or by using
a credit card.
Examination Schedule:
Please visit the 'Examination schedule' section on
https://www.softwarecertifications.org/exams/schedule.htm for updates on
locations & dates.
Common Body of Knowledge [CBoK]: The Common Body of Knowledge (CBoK) is
listed on www.softwarecertifications.org & defines the scope of the
examination. The application fee includes access to the Guide to the Body of
Knowledge which will help you prepare for the examination.
QAI does not provide any sample/mock papers as the examination is meant to
test your hands on experience at work.Its an examination based Certification and we do not provide any kind of training to any candidate. However, for preparation you can:-
1. You can refer to study guide provided to you after the registration.
2. You can get a list of reference books on www.softwarecertifications.org.
3. You can join some online forums like Yahoo, etc.
4. You can get in touch with people who are already certified (personally/online) for internal sessions.
To view the exam schedule, eligibility criteria, to apply for the
examination and for more information on these certifications, please visit
www.softwarecertifications.org
months (6 times a year) at Software Certifications Sponsored Test locations
and are written examinations.
Registration Process
Step 1:Register on the 'Customer Portal' section on
www.softwarecertifications.org
Step 2:Apply for Candidacy once you are logged in. You will have to enter
your Personal Info, Education, References, etc. in order to satisfy the
Candidacy Prerequisite checks. The Candidacy Payment Wizard will take you
through the payment process.
Step 3: You can Schedule an Examination when you feel ready to actually take
the Examination.
In order to take the written examination at these locations, you need to
register 30 days before the selected examination date by filling the form in
the 'Customer Portal' section on www.softwarecertifications.org and making
the required payment.
The eligibility criteria is available on
http://www.softwarecertifications.org
Payment Details:
CSQA & CSTE:
Option 1: US$350
[Application Fee+ Study Guide]
Option 2: US$420
[Application Fee + Study Guide + hard copy of the Study Guide]
CSPM: US$400
[Application Fee]
Mode: The fee (in US$ only) can be paid by a dollar draft/check or by using
a credit card.
Examination Schedule:
Please visit the 'Examination schedule' section on
https://www.softwarecertifications.org/exams/schedule.htm for updates on
locations & dates.
Common Body of Knowledge [CBoK]: The Common Body of Knowledge (CBoK) is
listed on www.softwarecertifications.org & defines the scope of the
examination. The application fee includes access to the Guide to the Body of
Knowledge which will help you prepare for the examination.
QAI does not provide any sample/mock papers as the examination is meant to
test your hands on experience at work.Its an examination based Certification and we do not provide any kind of training to any candidate. However, for preparation you can:-
1. You can refer to study guide provided to you after the registration.
2. You can get a list of reference books on www.softwarecertifications.org.
3. You can join some online forums like Yahoo, etc.
4. You can get in touch with people who are already certified (personally/online) for internal sessions.
To view the exam schedule, eligibility criteria, to apply for the
examination and for more information on these certifications, please visit
www.softwarecertifications.org
Steps to apply for ISTQB exams
Go to the site http://208.116.30.129/
Click "Exam Dates", there you can find the exam dates for various cities across india.
Check the examination schedule for your city.
Fill the Online Enrollment Form.A link for Enrollment form will be given in that same page
You would immediately receive a confirmation mail in your Personal ID along with further instructions.
As per instructions Send a D/D of amount specified in mail in favour of INDIAN TESTING BOARD, payable at 'NOIDA' to their Noida Office
Address to send DD is INDIAN TESTING BOARD
A-24, First Floor, Sector-59
NOIDA - 201301(U.P)
Then after one week they will send a payment confirmation mail
You will be informed of the timing and procedure of the examination. Appear for the examination on the designated date, time and venue.
Please do not forget to bring a photo identity (Passport, Driving License, Election Card etc.) with you when you appear for the examination.
You will be informed of your result within two weeks and passing candidates will receive the certificate within eight weeks.
If any enquiry related ISTQB and Sample question dumps and syllabus please contect me at prajeshbe@gmail.com
Click "Exam Dates", there you can find the exam dates for various cities across india.
Check the examination schedule for your city.
Fill the Online Enrollment Form.A link for Enrollment form will be given in that same page
You would immediately receive a confirmation mail in your Personal ID along with further instructions.
As per instructions Send a D/D of amount specified in mail in favour of INDIAN TESTING BOARD, payable at 'NOIDA' to their Noida Office
Address to send DD is INDIAN TESTING BOARD
A-24, First Floor, Sector-59
NOIDA - 201301(U.P)
Then after one week they will send a payment confirmation mail
You will be informed of the timing and procedure of the examination. Appear for the examination on the designated date, time and venue.
Please do not forget to bring a photo identity (Passport, Driving License, Election Card etc.) with you when you appear for the examination.
You will be informed of your result within two weeks and passing candidates will receive the certificate within eight weeks.
If any enquiry related ISTQB and Sample question dumps and syllabus please contect me at prajeshbe@gmail.com
Upcoming Schedule for ISTQB
Examination Schedule for Foundation Level
|
Advanced Level
| City | Date/Month/Time | Venue | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Ahmedabad |
| Technical Tester Functional Tester Test Manager Tops Technologies Pin: 380009 Contact No: 01204355270 Contact Person: Sonal Garg | ||||||||||||
| Bangalore |
| Technical Tester Functional Tester Test Manager St. Joseph's Pre-University College Opp. Good Shepherd Auditorium, Residency Road, Field Marshal Cariappa Road, Bangalore Pin: 560025 Contact No: 09343494617 Contact Person: Mr. Pravesh Pugalia Email: pravesh@indiantestingboard.com | ||||||||||||
| Chennai |
| Technical Tester Functional Tester Test Manager Meenakshi College For Women 363, Arcot Road, Kodambakkam, Chennai Pin: 600024 Contact No: 09343494617 Contact Person: Mr. Pravesh Pugalia Email: pravesh@indiantestingboard.com | ||||||||||||
| Cochin |
| 10.00-11.30 AM Technical Tester 11.45-1.15 PM Functional Tester 2.00-3.30 PM Test Manager St. Albert's College Banarji Road, Cochin Pin: 682018 Contact No: 0120-4236187 Contact Person: Miss Sonal Garg Email: sonal@indiantestingboard.com | ||||||||||||
| Coimbatore |
| 10.00-11.30 AM Technical Tester 11.45-1.15 PM Functional Tester 2.00-3.30 PM Test Manager Mazenet Maze Net Solution (P) Ltd., 12e,1st Floor,10th Street, Padmalaya Towers , Coimbatore - 12. Contact No: 01204236187 Contact Person: Sonal Garg Email: sonal@indiantestingboard.com | ||||||||||||
| Coimbatore |
| 10.00-11.30 AM Technical Tester 11.45-1.15 PM Functional Tester 2.00-3.30 PM Test Manager IIST 734, President Hall G.D.Naidu Charities Building, Avinashi Road, Coimbatore - 641018 Contact No: 01204236187 Contact Person: Sonal Garg Email: sonal@indiantestingboard.com | ||||||||||||
| Hyderabad |
| Technical Tester Functional Tester Test Manager Mind Q Mind Q Systems Pvt Ltd, 8-3-214/7, Srinivasa Nagar Colony (W), S.R.Nagar, Hyderabad Pin: 500038 Contact No: 0120-4236187 Contact Person: Miss Sonal Garg Email: sonal@indiantestingboard.com | ||||||||||||
| Indore |
| 10.00-11.30 AM Technical Tester 11.45-1.15 PM Functional Tester 2.00-3.30 PM Test Manager SQTL SQTL Integrated Solutions Pvt Ltd. 308, Akashdeep Complex 21, Sneh Nagar, Sapna-Sangeeta Main Road, Indore Contact Person: Miss Sonal Garg Email: sonal@indiantestingboard.com | ||||||||||||
| Kolkata |
| Technical Tester Functional Tester Test Manager Vallabhram Mehta Boys Secondary School 6 Pollock Street, Kolkata-700001 Pin: 700001 Contact No: 0120-4355270 Contact Person: Miss Sonal Garg Email: sonal@indiantesitngboard.com | ||||||||||||
| Madurai |
| 10.00-11.30 AM Technical Tester 11.45-1.15 PM Functional Tester 2.00-3.30 PM Test Manager Tandem Infotech Pvt .Ltd Opp.Ambiga Theatre, Anna Nagar, Madurai Pin: 625020 Contact No: 0120-4355270 Contact Person: Sonal Garg Email: sonal@indiantestingboard.com | ||||||||||||
| Mumbai |
| Technical Tester Functional Tester Test Manager Cosmopolitan’s Valia College of Commerce Near Versova Police Station D N Nagar, Cosmopolitian Education Society Road, Andheri(West) Mumbai Pin: 400053 Contact No: 0120-4236187 Contact Person: Miss Sonal Garg Email: sonal@indiantestingboard.com | ||||||||||||
| Nagpur |
| 10.00-11.30 AM Technical Tester 11.45-1.15 PM Functional Tester 2.00-3.30 PM Test Manager Vise India Vise India 1st Floor, Dhanwantaree Hospital, Khare Town, Dharampeth, Nagpur - 440 010 Pin: 440 010 Contact No: 01204236187 Contact Person: Sonal Garg Email: sonal@indiantestingboard.com | ||||||||||||
| Noida |
| Technical Tester Functional Tester Test Manager Indian Testing Board A-24, First Floor Sector-59 Noida Pin: 201301 Contact No: 0120-4236187 Contact Person: Miss Sonal Garg Email: sonal@indiantestingboard.com | ||||||||||||
| Pune |
| Technical Tester Functional Tester Test Manager Nowrosjee Wadia College 19, Late Principal V K Joag Path, Pune Pin: 411001 Contact No: 0120-4355270 Contact Person: Mr. Mohnesh Bakshi Email: mohnesh@indiantestingboard.com | ||||||||||||
| Tirunelveli |
| 10.00-11.30 AM Technical Tester 11.45-1.15 PM Functional Tester 2.00-3.30 PM Test Manager TANDEM TANDEM 124,Trivandrum Road, Opp.Siddha College(Next to IOB) Palayamkottai Tirunelveli Pin: 627 002 Contact No: 0120-4355270 Contact Person: Sonal Garg Email: sonal@indiantestingboard.com | ||||||||||||
| Trivandrum |
| Technical Tester Functional Tester Test Manager TIME Shiv Bhavan Opp SBI,Kannamoola, Medical College P.O., Trivandrum Pin: 695 011 Contact No: 0120-4236187 Contact Person: Sonal Garg Email: sonal@indiantestingboard.com |
Experience while writing the ISTQB certification
We planned to write our ISTQB certification as a team.
Gathered the ISTQB materials from the website http://www.istqb.org/download.htm
Also the sample questions from the various groups, communities and forums.
Each one read the material from starting to end and understood the meaning of each and every word given in the material. Then we had a discussion at least for one hour a day where we shared concept each of us understood .At last we will derive at the best answers for each concept .
Then we practiced our self by writing the sample test in the questions we collected from various sources.
Request for those writing the ISTQB examination
1.Read the ISTQB material thoroughly.
2.Workout with the sample papers by collecting through various groups, communities and forums.
3. Understand the concept clearly .
“TEAM WORK WINS”—IF YOUR TEAM IS MUTUAL THEN THE WORLD WILL BE ON YOUR FINGER TIPS
I am sure that if you follow this you will be an ISTQB certifier
Gathered the ISTQB materials from the website http://www.istqb.org/download.htm
Also the sample questions from the various groups, communities and forums.
Each one read the material from starting to end and understood the meaning of each and every word given in the material. Then we had a discussion at least for one hour a day where we shared concept each of us understood .At last we will derive at the best answers for each concept .
Then we practiced our self by writing the sample test in the questions we collected from various sources.
Request for those writing the ISTQB examination
1.Read the ISTQB material thoroughly.
2.Workout with the sample papers by collecting through various groups, communities and forums.
3. Understand the concept clearly .
“TEAM WORK WINS”—IF YOUR TEAM IS MUTUAL THEN THE WORLD WILL BE ON YOUR FINGER TIPS
I am sure that if you follow this you will be an ISTQB certifier
Fundamentals of testing
We need to understand, explain, give reasons, compare, classify, categorize, give examples and summarize;
Terms we need to understand in this Chapter are
1. Bug
2. Defect
3. Error
4. Failure
5. Fault
6. Mistake
7. Quality
8. Risk.
Error:
·Mistake made by the human beings
·An error or defect in software or Hardware that causes a program to malfunction
Defect :
* Due to mistake it produces a fault or bug in the code software or a system, or in a document.
* A defect is any variance between actual and expected results.
Failure :
* If a defect in code is executed, the system will fail to do
* what it should do or do something it shouldn’t
So the relation is
Error =>Defect=>Failure
Defect :
* Problem in algorithm leads to failure
* Non conformance to requirements or functional / program specification
Bug:
* Deviation from the expected result.
* It is a fault in a program which causes the program to perform in an unintended or unanticipated manner
Causes for Defects:
Defects occur because human beings are fallible and because there is
* time pressure,
* complex code,
* complexity of infrastructure,
* changed technologies, and/or many system interactions.
Causes for Failures
Failures can be caused by
* environmental conditions as well: radiation, magnetism, electronic fields,
* pollution can cause faults in firmware or influence the execution of software by changing
* hardware conditions.
Purpose of testing :
* Reduce the risk
* Contribute to the quality of the software system
* Could give confidence in the quality of the software if it finds few or no defects
Quality assurance :
Lesson Learnt from the previous projects and by understanding the root cause of defects found in other projects, processes can be improved, which in turn should prevent those defects from
Reoccurring and, as a consequence, improve the quality of future systems.
What is Risk?
Uncertainty — An event may occur or may not occur
Why is Risk arises?
• Uncertainty
• Inexperience
• Inability to accurately forecast
How much testing is enough?
* Level of risk, including technical and business product and project risks,
* Project constraints such as time and budget
Terms we need to understand in this Chapter are
1. Bug
2. Defect
3. Error
4. Failure
5. Fault
6. Mistake
7. Quality
8. Risk.
Error:
·Mistake made by the human beings
·An error or defect in software or Hardware that causes a program to malfunction
Defect :
* Due to mistake it produces a fault or bug in the code software or a system, or in a document.
* A defect is any variance between actual and expected results.
Failure :
* If a defect in code is executed, the system will fail to do
* what it should do or do something it shouldn’t
So the relation is
Error =>Defect=>Failure
Defect :
* Problem in algorithm leads to failure
* Non conformance to requirements or functional / program specification
Bug:
* Deviation from the expected result.
* It is a fault in a program which causes the program to perform in an unintended or unanticipated manner
Causes for Defects:
Defects occur because human beings are fallible and because there is
* time pressure,
* complex code,
* complexity of infrastructure,
* changed technologies, and/or many system interactions.
Causes for Failures
Failures can be caused by
* environmental conditions as well: radiation, magnetism, electronic fields,
* pollution can cause faults in firmware or influence the execution of software by changing
* hardware conditions.
Purpose of testing :
* Reduce the risk
* Contribute to the quality of the software system
* Could give confidence in the quality of the software if it finds few or no defects
Quality assurance :
Lesson Learnt from the previous projects and by understanding the root cause of defects found in other projects, processes can be improved, which in turn should prevent those defects from
Reoccurring and, as a consequence, improve the quality of future systems.
What is Risk?
Uncertainty — An event may occur or may not occur
Why is Risk arises?
• Uncertainty
• Inexperience
• Inability to accurately forecast
How much testing is enough?
* Level of risk, including technical and business product and project risks,
* Project constraints such as time and budget
Principles of testing
A number of testing principles have been suggested over the past 40 years and offer general
guidelines common for all testing.
Principle 1 – Testing shows presence of defects
Testing can show that defects are present, but cannot prove that there are no defects.
Testing reduces the probability of undiscovered defects remaining in the software but, even if no defects are found, it is not a proof of correctness.
Principle 2 – Exhaustive testing is impossible
Testing everything (all combination of inputs and preconditions) is not feasible except for trivial
cases.
Principle 3 – Early testing
Testing activities should start as early as possible in the software or system development life cycle,
and should be focused on defined objectives
Principle 4 – Defect clustering
A small number of modules contain most of the defects discovered during pre-release testing, or
are responsible for the most operational failures.
Principle 5 – Pesticide paradox
If the same tests are repeated over and over again, eventually the same set of test cases will no
longer find any new defects. To overcome this “pesticide paradox”, the test cases need to be
regularly reviewed and revised, and new and different tests need to be written to exercise different
parts of the software or system to potentially find more defects.
Principle 6 – Testing is context dependent
Testing is done differently in different contexts. For example, safety-critical software is tested
differently from an e-commerce site.
Principle 7 – Absence-of-errors fallacy
Finding and fixing defects does not help if the system built is unusable and does not fulfill the users’
guidelines common for all testing.
Principle 1 – Testing shows presence of defects
Testing can show that defects are present, but cannot prove that there are no defects.
Testing reduces the probability of undiscovered defects remaining in the software but, even if no defects are found, it is not a proof of correctness.
Principle 2 – Exhaustive testing is impossible
Testing everything (all combination of inputs and preconditions) is not feasible except for trivial
cases.
Principle 3 – Early testing
Testing activities should start as early as possible in the software or system development life cycle,
and should be focused on defined objectives
Principle 4 – Defect clustering
A small number of modules contain most of the defects discovered during pre-release testing, or
are responsible for the most operational failures.
Principle 5 – Pesticide paradox
If the same tests are repeated over and over again, eventually the same set of test cases will no
longer find any new defects. To overcome this “pesticide paradox”, the test cases need to be
regularly reviewed and revised, and new and different tests need to be written to exercise different
parts of the software or system to potentially find more defects.
Principle 6 – Testing is context dependent
Testing is done differently in different contexts. For example, safety-critical software is tested
differently from an e-commerce site.
Principle 7 – Absence-of-errors fallacy
Finding and fixing defects does not help if the system built is unusable and does not fulfill the users’
Software Testing Types
* COMPATIBILITY TESTING. Testing to ensure compatibility of an application or Web site with different browsers, OS, and hardware platforms. Compatibility testing can be performed manually or can be driven by an automated functional or regression test suite.
* FUNCTIONAL TESTING. Validating an application or Web site conforms to its specifications and correctly performs all its required functions. This entails a series of tests which perform a feature by feature validation of behavior, using a wide range of normal and erroneous input data. This can involve testing of the product’s user interface, APIs, database management, security, installation, networking, etc testing can be performed on an automated or manual basis using black box or white box methodologies.
* LOAD TESTING. Load testing is a generic term covering Performance Testing and Stress Testing.
* PERFORMANCE TESTING. Performance testing can be applied to understand your application or WWW site’s scalability, or to benchmark the performance in an environment of third party products such as servers and middle ware for potential purchase. This sort of testing is particularly useful to identify performance bottlenecks in high use applications. Performance testing generally involves an automated test suite as this allows easy simulation of a variety of normal, peak, and exceptional load conditions.
* REGRESSION TESTING. Similar in scope to a functional test, a regression test allows a consistent, repeatable validation of each new release of a product or Web site. Such testing ensures reported product defects have been corrected for each new release and that no new quality problems were introduced in the maintenance process. Though regression testing can be performed manually an automated test suite is often used to reduce the time and resources needed to perform the required testing.
* SMOKE TESTING. A quick-and-dirty test that the major functions of a piece of software work without bothering with finer details. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.
* STRESS TESTING. Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. A graceful degradation under load leading to non-catastrophic failure is the desired result. Often Stress Testing is performed using the same process as Performance Testing but employing a very high level of simulated load.
* UNIT TESTING. Functional and reliability testing in an Engineering environment. Producing tests for the behavior of components of a product to ensure their correct behavior prior to system integration.
* FUNCTIONAL TESTING. Validating an application or Web site conforms to its specifications and correctly performs all its required functions. This entails a series of tests which perform a feature by feature validation of behavior, using a wide range of normal and erroneous input data. This can involve testing of the product’s user interface, APIs, database management, security, installation, networking, etc testing can be performed on an automated or manual basis using black box or white box methodologies.
* LOAD TESTING. Load testing is a generic term covering Performance Testing and Stress Testing.
* PERFORMANCE TESTING. Performance testing can be applied to understand your application or WWW site’s scalability, or to benchmark the performance in an environment of third party products such as servers and middle ware for potential purchase. This sort of testing is particularly useful to identify performance bottlenecks in high use applications. Performance testing generally involves an automated test suite as this allows easy simulation of a variety of normal, peak, and exceptional load conditions.
* REGRESSION TESTING. Similar in scope to a functional test, a regression test allows a consistent, repeatable validation of each new release of a product or Web site. Such testing ensures reported product defects have been corrected for each new release and that no new quality problems were introduced in the maintenance process. Though regression testing can be performed manually an automated test suite is often used to reduce the time and resources needed to perform the required testing.
* SMOKE TESTING. A quick-and-dirty test that the major functions of a piece of software work without bothering with finer details. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.
* STRESS TESTING. Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. A graceful degradation under load leading to non-catastrophic failure is the desired result. Often Stress Testing is performed using the same process as Performance Testing but employing a very high level of simulated load.
* UNIT TESTING. Functional and reliability testing in an Engineering environment. Producing tests for the behavior of components of a product to ensure their correct behavior prior to system integration.
Difference between Client/ Server testing and web based testing
Projects are broadly divided into two types of :
· 2 tier applications
· 3 tier applications
CLIENT / SERVER TESTING
[a] This type of testing usually done for 2 tier applications (usually developed for LAN)
Here we will be having front end and back end.
The application launched on front end will be having forms and reports which will be monitoring and manipulating data
Eg : applications developed in VB,VC++,Core Java,C,C++,D2K,Power Builder etc.,
The back end for these applications would be MS Access, SQL Server, oracle, sybase, mysql, quadbase
The tests performed on these type of applications would be
- user interface testing
- manual support testing
- Functionality testing
- compatibility testing & configuration testing
- inter systems testing
WEB TESTING
[b] This is done for 3 tier applications (developed for Internet / intranet / xtranet)
Here we will be having Browser, web server and DB server.
The applications accessible in browser would be developed in HTML, DHTML, XML, JavaScript etc.,
(we can monitor through these applications)
Applications for the web server would be developed in Adv Java, ASP, JSP, VB Script, JavaScript, Perl, Cold Fusion, PHP etc.,
(all the manipulations are done on the web server with the help of these programs developed)
The DB server would be having oracle, sql server, sybase, mysql etc.,
(all data is stored in the database available on the DB server)
The tests performed on these type of applications would be
- user interface testing
- Functionality testing
- security testing
- browser compatibility testing
- load / stress testing
- interoperability testing/inter systems testing
- storage and data volume testing
· 2 tier applications
· 3 tier applications
CLIENT / SERVER TESTING
[a] This type of testing usually done for 2 tier applications (usually developed for LAN)
Here we will be having front end and back end.
The application launched on front end will be having forms and reports which will be monitoring and manipulating data
Eg : applications developed in VB,VC++,Core Java,C,C++,D2K,Power Builder etc.,
The back end for these applications would be MS Access, SQL Server, oracle, sybase, mysql, quadbase
The tests performed on these type of applications would be
- user interface testing
- manual support testing
- Functionality testing
- compatibility testing & configuration testing
- inter systems testing
WEB TESTING
[b] This is done for 3 tier applications (developed for Internet / intranet / xtranet)
Here we will be having Browser, web server and DB server.
The applications accessible in browser would be developed in HTML, DHTML, XML, JavaScript etc.,
(we can monitor through these applications)
Applications for the web server would be developed in Adv Java, ASP, JSP, VB Script, JavaScript, Perl, Cold Fusion, PHP etc.,
(all the manipulations are done on the web server with the help of these programs developed)
The DB server would be having oracle, sql server, sybase, mysql etc.,
(all data is stored in the database available on the DB server)
The tests performed on these type of applications would be
- user interface testing
- Functionality testing
- security testing
- browser compatibility testing
- load / stress testing
- interoperability testing/inter systems testing
- storage and data volume testing
What we will do in Manual Testing?
1. Understand the functionality of program
2. Prepare a test environment
3. Execute test case(s) manually
4. Verify the actual result
5. Record the result as Pass or Fail
6. Make a summary report of the Pass and Fail test cases
7. Publish the report
8. Record any new defects uncovered during the test case execution
2. Prepare a test environment
3. Execute test case(s) manually
4. Verify the actual result
5. Record the result as Pass or Fail
6. Make a summary report of the Pass and Fail test cases
7. Publish the report
8. Record any new defects uncovered during the test case execution
Flow of testing
Before testing any application we should follow some standard flow.
Generic Testing flow is as follows
1. Smoke Testing
2. Sanity Testing
3. Component testing
4. Integration testing
5. System testing
6. Acceptance testing
Smoke testing is originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke... We will be concentrating on Basic functionality of the product. It is also called as Build verification testing
In Sanity Testing we will be focusing on the major functionality or the functionality in detail. It is the subset of Regression testing
In Component Testing we will be testing module by module
In Integration testing one or more modules are combined and tested. Eg: In larger domains like Telecom, there will be many modules so we will be integrating the modules and will be testing
In System testing all the modules are combined and the whole application is tested
Acceptance testing will be done to ensure the confidence in the system and it is done mainly by the end users
Note:
The flow of testing varies depending on the organization
Generic Testing flow is as follows
1. Smoke Testing
2. Sanity Testing
3. Component testing
4. Integration testing
5. System testing
6. Acceptance testing
Smoke testing is originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke... We will be concentrating on Basic functionality of the product. It is also called as Build verification testing
In Sanity Testing we will be focusing on the major functionality or the functionality in detail. It is the subset of Regression testing
In Component Testing we will be testing module by module
In Integration testing one or more modules are combined and tested. Eg: In larger domains like Telecom, there will be many modules so we will be integrating the modules and will be testing
In System testing all the modules are combined and the whole application is tested
Acceptance testing will be done to ensure the confidence in the system and it is done mainly by the end users
Note:
The flow of testing varies depending on the organization
Basics of Software Testing
“Testing is a skill. While this may come as a surprise to some people, it is a simple fact”
Software Testing:
Software testing is the process of finding the defects as soon as possible and fixing them before delivering products to the client and also verify that the application meets the client’s requirement.
This increases the “Quality” of the product and decreases the “Risk”
Importance of Testing:
It Increases Customer satisfaction and the number of customers as well.
It Increases the Quality of the application.
It Increases the reputation of the organization.
Methods of Testing:
1) Manual Testing
2) Automation Testing
Levels of Testing:
1) Unit testing
2) Integration testing
3) System Testing
4) Acceptance testing
Types of Testing: (For Web Applications)
Unit Testing:
Done by Developers.
Functional Testing:
1) Sanity Testing
2) Smoke Testing
3) Component Testing
4) Integration Testing
5) Regression Testing
6) URL Testing
7) System Testing
8) Globalization and Localization Testing
Non-Functional Testing:
1) Load Testing
2) Performance Testing
3) Compatibility Testing
4) Installation Testing
5) Usability Testing
6) User Interface Testing
7) Security Testing
Software Testing:
Software testing is the process of finding the defects as soon as possible and fixing them before delivering products to the client and also verify that the application meets the client’s requirement.
This increases the “Quality” of the product and decreases the “Risk”
Importance of Testing:
It Increases Customer satisfaction and the number of customers as well.
It Increases the Quality of the application.
It Increases the reputation of the organization.
Methods of Testing:
1) Manual Testing
2) Automation Testing
Levels of Testing:
1) Unit testing
2) Integration testing
3) System Testing
4) Acceptance testing
Types of Testing: (For Web Applications)
Unit Testing:
Done by Developers.
Functional Testing:
1) Sanity Testing
2) Smoke Testing
3) Component Testing
4) Integration Testing
5) Regression Testing
6) URL Testing
7) System Testing
8) Globalization and Localization Testing
Non-Functional Testing:
1) Load Testing
2) Performance Testing
3) Compatibility Testing
4) Installation Testing
5) Usability Testing
6) User Interface Testing
7) Security Testing
Inroduction
I proudly present this blog to the members who are new to software testing field
and the people who are having eager to know the concept, process and definitions of testing clearly.
I have 4 years of experience in software testing and also got ISTQB and Expert Rating certification.I have participated in so many blogs as a member for the past three years and now i have started my own blog in software testing field.
The posts in this site are based upon my real-time experiences.
please email me to prajeshbe@gmail.com,if you have any doubts
Moderator,
softwaretestingwinners.blogspot.com
and the people who are having eager to know the concept, process and definitions of testing clearly.
I have 4 years of experience in software testing and also got ISTQB and Expert Rating certification.I have participated in so many blogs as a member for the past three years and now i have started my own blog in software testing field.
The posts in this site are based upon my real-time experiences.
please email me to prajeshbe@gmail.com,if you have any doubts
Moderator,
softwaretestingwinners.blogspot.com
Subscribe to:
Posts (Atom)