Software Testing Guide
Software Testing Guide
Next Blog
Create Blog
Sign In
Search
LINKS
QTP Guide Quality Center (QC) Guide SQL Server Guide Winrunner FAQs
JU L Y 11, 2011
Ads by Google Software Testing Application Testing Testing Tools Testing Training
Agile testing is useful whenever the customer requirements are changing frequently.
PRE V I OUS POSTS
0 c o mme n t s
Explain Agile Testing. Define CVS. Explain the different types of Severity. What is Bucket Testing? What is Entry and Exit Criteria in Software Testin... What is Concurrency Testing? What is the difference between Functional Requirem... Explain Statement Coverage / Code Coverage / Line ... Explain Branch Coverage / Decision Coverage. What is the difference between High level and Low ...
M A Y 30, 2011
Define CVS.
CVS is Concurrent Versioning System which is a version control system, where the history of sources files can be recorded.
The main advantages of CVS are, You can save each file of every version. After modifications in source, if u detect a bug, you can easily retrieve the old version to check which change caused that bug. CVS can be used to merge the work done by all the developers.
0 c o mme n t s
JU L Y 13, 2010
BDS Courses
Admissions Open For 2011 Scholarships Available. Apply Now !
Sha rda .a c.in
JU NE 30, 2010
The Exit Criteria ensures whether testing is completed and the application is ready for release, like, Test Summary Report Metrics Defect Analysis Report.
P O STED B Y J ERRY RU B AN AT 12:43 PM 1 c o mme n t s
A RCHIV ES
27 August 2006 03 September 2006 10 September 2006 Bookmark this Blog to your Favorites 17 September 2006 08 October 2006
JU NE 11, 2010
05 November 2006 12 November 2006 24 December 2006 14 January 2007 21 January 2007 26 August 2007 23 September 2007 22 June 2008 21 September 2008 12 October 2008 23 November 2008 14 December 2008 21 December 2008 18 January 2009
0 c o mme n t s
Ex. Load runner is widely used for this type of testing, Vugen (Virtual User Generator) is used to add the number of concurrent users and how the users need to be added like Gradual Rampup or Spike Stepped.
P O STED B Y J ERRY RU B AN AT 5:46 P M
31 May 2009 28 June 2009 06 September 2009 20 September 2009 25 October 2009 22 November 2009
What is the difference between Functional Requirement and Non Functional Requirement?
The Functional Requirement specifies how the system or application SHOULD DO where in Non Functional Requirement it specifies how the system or application SHOULD BE.
Some Functional Requirements are, Authentication Business Rules Historical Data Legal and Regulatory Requirements External Interfaces Some Non Functional Requirements are, Performance Reliability Security Recovery Data Integrity Usability
P O STED B Y J ERRY RU B AN AT 6:02 P M 0 c o mme n t s
27 December 2009 24 January 2010 11 April 2010 06 June 2010 27 June 2010 11 July 2010 19 September 2010 29 May 2011 10 July 2011
JA NU A RY 27, 2010
Some advantages of Statement Coverage / Code Coverage / Line Coverage are, It verifies what the written code is expected to do and not to do. It measures the quality of code written. It checks the flow of different paths in the program also ensure whether those paths are tested or not.
To Calculate Statement Coverage, Statement Coverage = Statements Tested / Total No. of Statements.
P O STED B Y J ERRY RU B AN AT 5:52 P M 2 c o mme n t s
DE CE M BE R 2 9 , 20 0 9
To Calculate Branch Coverage, Branch Coverage = Tested Decision Outcomes / Total Decision Outcomes.
P O STED B Y J ERRY RU B AN AT 3:25 P M 6 c o mme n t s
What is the difference between High level and Low level test cases?
High level Test cases are those which covers major functionality in the application (i.e. retrieve, update display, cancel (functionality related test cases), database test cases).
Low level test cases are those related to User Interface (UI) in the application.
0 c o mme n t s
Testing Jobs
Exp:0-5yrs, Sal:2080k Submit CV to Apply
Monste rIndia .com
In terms of Localization Testing it verifies how correctly the application is changed or modified into that target culture and language.
In case of translation required of the application on that local language, testing should be done on each field to check the correct translation. Other formats like date conversion, hardware and software usage like operating system should also be considered in localization testing.
Examples for Localization Testing are, In Islamic Banking all the transactions and product features are based on Shariah Law, some important points to be noted in Islamic Banking are, 1.In Islamic Banking, the bank shares the profit and loss with the customer. 2.In Islamic Banking, the bank cannot charge interest on the customer; instead they charge a nominal fee which is termed as Profit. 3.In Islamic Banking, the bank will not deal or invest in business like Gambling, Alcohol, Pork, etc. In this case, we need to test whether these Islamic banking conditions were modified and applied in the application or product.
In Islamic Lending, they follow both the Gregorian Calendar and Hijiri Calendar for calculating the loan repayment schedule. The Hijiri Calendar is commonly called as Islamic Calendar followed in all the Muslim countries according to the lunar cycle. The Hijiri Calendar has 12 months and 354 days which is 11 days shorter than Gregorian Calendar. In this case, we need to test the repayment schedule by comparing both the Gregorian Calendar and Hijiri Calendar.
P O STED B Y J ERRY RU B AN AT 3:07 P M 4 c o mme n t s
In Software Testing some unavoidable risk might takes place like, Change in requirements or Incomplete requirements. Time allocation for testing. Developers delaying to deliver the build for testing. Urgency from client for delivery. Defect Leakage due to application size or complexity.
To overcome these risks, the following activities can be done, Conducting Risk Assessment review meeting with the development team. Profile for Risk coverage is created by mentioning the importance of each area. Using maximum resources to work on High Risk areas like allocating more testers for High risk areas and minimum resources for Medium and Low risk areas.Creation of Risk assessment database for future maintenance and management review.
P O STED B Y J ERRY RU B AN AT 12:57 PM 2 c o mme n t s
2 c o mme n t s
What is the difference between Two Tier Architecture and Three Tier Architecture?
In Two Tier Architecture or Client/Server Architecture two layers like Client and Server is involved. The Client sends request to Server and the Server responds to the request by fetching the data from it. The problem with the Two Tier Architecture is the server cannot respond to multiple requests at the same time which causes data integrity issues. The Client/Server Testing involves testing the Two Tier Architecture of user interface in the front end and database as backend with dependencies on Client, Hardware and Servers. In Three Tier Architecture or Multi Tier Architecture three layers like Client, Server and Database are involved. In this the Client sends a request to Server, where the Server sends the request to Database for data, based on that request the Database sends back the data to Server and from Server the data is forwarded to Client. The Web Application Testing involves testing the Three Tier Architecture including the User interface, Functionality, Performance, Compatibility, Security and Database testing.
P O STED B Y J ERRY RU B AN AT 6:58 AM 2 c o mme n t s
JU L Y 2, 2009
JU NE 1, 2009
Explain Use case diagrams. What are the attributes of use cases?
Use Case Diagrams is an overview graphical representation of the functionality in a system. It is used in the analysis phase of a project to specify the system to be developed.
In Use Case Diagrams the whole system is defined as ACTORS, USE CASES and ASSOCIATIONS, the ACTORS are the external part of the system like users, computer software & hardware, USECASES is the behavior or functionality of the system when these ACTORS perform an action, the ASSOCIATIONS are the line drawn to show the connection between ACTORS and USECASES. One ACTOR can link to many USECASES and one USECASE can link to many ACTORS.
P O STED B Y J ERRY RU B AN AT 4:01 P M 0 c o mme n t s
What is Web Application Testing? Explain the different phases in Web Application Testing.
Web Application Testing is done on a website to check its load, performance, Security, Functionality, Interface, compatibility and other usability related issues. In Web application testing, three phases of testing is done, they are, Web Tier Testing In Web tier testing, the browser compatibility of the application will be tested for IE, FireFox and other web browsers. Middle Tier Testing In Middle tier testing, the functionality and security issues were tested. Database Tier Testing In Database tier testing, the database integrity and the contents of the database were tested and verified.
P O STED B Y J ERRY RU B AN AT 7:18 AM 0 c o mme n t s
M A RCH 3, 2009
Explain Unit Testing, Interface Testing and Integration Testing. Also explain the types of Integration Testing in brief.
Unit Testing Unit Testing is done to check whether the individual modules of the source code is working properly. i.e Testing each and every unit of the application separately by the developer in developers environment. Interface Testing Interface Testing is done to check whether the individual modules are communicating properly one among other as per the specifications. Interface Testing is mostly used in testing the user interface of GUI applications. Integration Testing Integration Testing is done to check the connectivity by combining all the individual modules together and test the functionality. The types of Integration Testing are, 1) Big Bang Integration Testing In Big Bang Integration Testing, the individual modules are not integrated until all the modules are ready. Then they will run to check whether it is performing well. In this type of testing, some disadvantages might occur like, Defects can be found at the later stage. It would be difficult to find out whether the defect arouse in Interface or in module. 2) Top Down Integration Testing In Top Down Integration Testing, the high level modules are integrated and tested first. i.e Testing from main module to sub module. In this type of testing, Stubs are used as temporary module if a module is not ready for integration testing. 3) Bottom Up Integration Testing In Bottom Up Integration Testing, the low level modules are integrated and tested first i.e Testing from sub module to main module. Same like Stubs, here drivers are used as a temporary module for integration testing.
P O STED B Y J ERRY RU B AN AT 8:41 P M 1 c o mme n t s
FEBRUA RY 7, 2009
1 c o mme n t s
JA NU A RY 18, 2009
Black Box Level Session Hijacking Session Hijacking commonly called as IP Spoofing where a user session will be attacked on a protected network. Session Prediction Session Prediction is a method of obtaining data or a session ID of an authorized user and gets access to the application. In a web application the session ID can be retrieved from cookies or URL. The Session Prediction happening can be predicted when a website is not responding normally or stops responding for an unknown reason. Email Spoofing Email Spoofing is duplicating the email header (From address) to look like originated from actual source and if the email is replied it will land in the spammers inbox. By inserting commands in the header the message information can be altered. It is possible to send a spoofed email with information you didnt write. Content Spoofing Content spoofing is a technique to develop a fake website and make the user believe that the information and website is genuine. When the user enters his Credit Card Number, Password, SSN and other important details the hacker can get the data and use if for fraud purposes. Phishing Phishing is similar to Email Spoofing where the hacker sends a genuine look like mail attempting to get the personal and financial information of the user. The emails will appear to have come from well known websites. Password Cracking Password Cracking is used to identify an unknown password or to identify a forgotten password Password cracking can be done through two ways, 1. Brute Force The hacker tries with a combination of characters within a length and tries until it is getting accepted. 2. Password Dictionary The hacker uses the Password dictionary where it is available on various topics.
White Box Level Malicious Code Injection SQL Injection is most popular in Code Injection Attack, the hacker attach the malicious code into the good code by inserting the field in the application. The motive behind the injection is to steal the secured information which was intended to be used by a set of users. Apart from SQL Injection, the other types of Malicious code injection are XPath Injection, LDAP Injection, and Command Execution Injection. Similar to SQL Injection the XPath Injection deals with XML document. Penetration Testing Penetration Testing is used to check the security of a computer or a network. The test process explores all the security aspects of the system and tries to penetrate the system. Input Validation Input validation is used to defend the applications from hackers. If the input is not
validated mostly in web applications it could lead to system crashes, database manipulation and corruption. Variable Manipulation Variable manipulation is used as a method for specifying or editing the variables in a program. It is mostly used to alter the data sent to web server. Database Level SQL Injection SQL Injection is used to hack the websites by changing the backend SQL statements, using this technique the hacker can steal the data from database and also delete and modify it.
P O STED B Y J ERRY RU B AN AT 4:29 P M 1 c o mme n t s
DE CE M BE R 2 2 , 20 0 8
DE CE M BE R 1 7 , 20 0 8
Level 4 In this level various metrics are used to follow the process and products. The delivery quality is high.
Level 5 In this level new process and technology were used and implemented efficiently. The objective will be for consistence process development. ISO refers to 'International Organization for Standardization', the ISO 9001:2000 standard is used for quality systems audited by outside auditors. This standard is applicable for manufacturing companies not only for software. This standard is given based on the documentation, design, production, testing, servicing and other processes. IEEE refers to 'Institute of Electrical and Electronics Engineers', which has members from many technical professional organizations around the world. IEEE 829 is the standard followed for software test documentation.
ANSI refers to 'American National Standards Institute', which manages the development of standards for products, services, personnel, processes, and systems in U.S. This organization also works with other international standards to make use of American products worldwide.
P O STED B Y J ERRY RU B AN AT 8:40 AM 4 c o mme n t s
Explain Test Plan, Test Strategy, Test Scenario, Test Case, Test Script, Test Environment, Test Procedure and Test Log.
Test Plan: Test Plan is a document with information on Scope of the project, Approach, Schedule of testing activities, Resources or Manpower required, Risk Issues, Features to be tested and not to be tested, Test Tools and Environment Requirements. Test Strategy: Test Strategy is a document prepared by the Quality Assurance Department with the details of testing approach to reach the Quality standards. Test Scenario: Test Scenario is prepared based on the test cases and test scripts with the sequence of execution. Test Case: Test case is a document normally prepared by the tester with the sequence of steps to test the behavior of feature/functionality/non-functionality of the application. Test Case document consists of Test case ID, Test Case Name, Conditions (Pre and Post Conditions) or Actions, Environment, Expected Results, Actual Results, Pass/Fail. The Test cases can be broadly classified as User Interface Test cases, Positive Test cases and Negative Test cases. Test Script: Test Script is a program written to test the functionality of the application. It is a set of system readable instructions to automate the testing with the advantage of doing repeatable and regression testing easily. Test Environment: It is the Hardware and Software Environment where is the testing is going to be done. It also explains whether the software under test interacts with Stubs and Drivers. Test Procedure: Test Procedure is a document with the detailed instruction for step by step execution of one or more test cases. Test procedure is used in Test Scenario and Test Scripts. Test Log: Test Log contains the details of test case execution and the output information.
P O STED B Y J ERRY RU B AN AT 7:32 AM 5 c o mme n t s
JU NE 22, 2008
like
Operating
System,
Database,
Browser
compatibility,
Backwards
Say for example if there is an application which can handle 25 simultaneous user logins at a time. In load testing we will test the application for 25 users and check how application is working in this stage, in performance testing we will concentrate on the time taken to perform the operation. Where as in stress testing we will test with more users than 25 and the test will continue to any number and we will check where the application is cracking the Hardware resources.
P O STED B Y J ERRY RU B AN AT 9:01 P M 6 c o mme n t s
JA NU A RY 23, 2007
Explain Boundary value testing and Equivalence testing with some examples.
Boundary value testing is a technique to find whether the application is accepting the expected range of values and rejecting the values which falls out of range. Ex. A user ID text box has to accept alphabet characters ( a-z ) with length of 4 to 10 characters. BVA is done like this, max value:10 pass; max-1: 9 pass; max+1=11 fail ;min=4 pass;min+1=5 pass;min-1=3 fail; Like wise we check the corner values and come out with a conclusion whether the application is accepting correct range of values. Equivalence testing is normally used to check the type of the object. Ex. A user ID text box has to accept alphabet characters ( a - z ) with length of 4 to 10 characters. In +ve condition we have test the object by giving alphabets. i.e a-z char only, after that we need to check whether the object accepts the value, it will pass. In -ve condition we have to test by giving other than alphabets (a-z) i.e A-Z,0-9,blank etc, it will fail.
P O STED B Y J ERRY RU B AN AT 3:06 P M 8 c o mme n t s
JA NU A RY 17, 2007
It is a process used to look out whether the security features of a system are implemented as designed and also whether they are adequate for a proposed application environment. verification.
P O STED B Y J ERRY RU B AN AT 3:12 P M 0 c o mme n t s
This
process
involves
functional
testing,
penetration
testing
and
DE CE M BE R 2 7 , 20 0 6
What is AUT ?
AUT is nothing but "Application Under Test". After the designing and coding phase in Software development life cycle, the application comes for testing then at that time the application is stated as Application Under Test.
P O STED B Y J ERRY RU B AN AT 11:49 AM 3 c o mme n t s
Error Seeding is the process of adding known faults intentionally in a program for the reason of monitoring the rate of detection & removal and also to estimate the number of faults remaining in the program.
P O STED B Y J ERRY RU B AN AT 3:35 P M 2 c o mme n t s
Test Data is that run through a computer program to test the software. Test data can be used to test the compliance with effective controls in the software.
P O STED B Y J ERRY RU B AN AT 12:45 PM 2 c o mme n t s
STLC System Study Test planning Writing Test case or scripts Review the test case Executing test case Bug tracking Report the defect
P O STED B Y J ERRY RU B AN AT 3:15 P M 4 c o mme n t s
Top-down approach : In this approach testing is conducted from main module to sub module. if the sub module is not developed a temporary program called STUB is used for simulate the submodule.
P O STED B Y J ERRY RU B AN AT 3:22 P M 8 c o mme n t s
Structural testing is a "white box" testing and it is based on the algorithm or code.
Functional testing is a "black box" (behavioral) testing where the tester verifies the functional specification.
Regression Testing - Testing the application after a change in a module or part of the application for testing that is the code change will affect rest of the application.
P O STED B Y J ERRY RU B AN AT 11:23 AM 5 c o mme n t s
What are the basic solutions for the software development problems?
Basic requirements - clear, detailed, complete, achievable, testable requirements has to be developed. Use some prototypes to help pin down requirements. In nimble environments, continuous and close coordination with customers/end-users is needed.
Schedules should be realistic - enough time to plan, design, test, bug fix, re-test, change, and document in the given schedule.
Adequate testing testing should be started early, it should be re-tested after the bug fixed or changed, enough time should be spend for testing and bug-fixing.
Proper study on initial requirements be ready to look after more changes after the development has begun and be ready to explain the changes done to others. Work closely with the customers and end-users to manage expectations. This avoids excessive changes in the later stages.
Communication conduct frequent inspections and walkthroughs in appropriate time period; ensure that the information and the documentation is available on up-to-date if possible electronic. More emphasize on promoting teamwork and cooperation inside the team; use prototypes and proper communication with the end-users to clarify their doubts and expectations.
P O STED B Y J ERRY RU B AN AT 11:14 AM 1 c o mme n t s
Unrealistic schedules Sometimes too much of work is being given to the developer and ask him to complete in a Short duration, then the problems are unavoidable.
Insufficient testing The problems can arise when the developed software is not tested properly.
Given another work under the existing process request from the higher management to work on another project or task will bring some problems when the project is being tested as a team.
Miscommunication in some cases, the developer was not informed about the Clients requirement and expectations, so there can be deviations.
P O STED B Y J ERRY RU B AN AT 10:26 AM 0 c o mme n t s
Ads by Google
Functional Testing
Load Testing
Automated Testing
Testing Training
Performance Testing