Thursday, November 27, 2008

Basic UNIX

UNIX was developed at AT&T’s Bell Laboratories after Bell Labs withdrew from a long-term collaboration with General Electrics (E) and MIT to create an operating system called MULTICS (Multiplexed Operating and Computing System) for G.E’s mainframe. In 1969, Bell Labs researchers created the first version of UNIX (then called UNICS, or Uniplexed Operating and Computing System) which has evolved over time to come to today’s Unix system.Here are few very popular UNIX flavors available today
Solaris Unix
Hewlett Packard HP-UX
Yellow Dog Linux (for apple system)
SCO OpenServer
Red Hat Enterprise Linux
SGI-IRIX
Fedora Core
SUSE Linux
Debian GNU
Mac OS X
FreeBSD
OpenBSD
KNOPPIX
NetBSD
OS/390 Unix
Plan 9Unix system is made up of different components that make Unix operating system such as a) Unix Kernelb) The Shellc) The File system, and the utilities.Unix Kernel is the lowest layer of the Unix system. The Kernel controls processes, input/output devices, file system operations, and manages memory.Shell is a command line interpreter used to interact between the users and operating system. Shell is used to administer and run system directly such as typing commands in the command line and executing them. There are many Shells available today amongst which three are very popular: the Bourne Shell (sh, bash), the C shell (csh), the Korn shell (ksh).Unix Utilities are important to enable system to run such as file system is one of the Unix utility that enables users to view, interact, and organize files and directories.

Tuesday, November 18, 2008

Recently popular web testing tool - Selenium

Selenium is a open source web testing tool. You can download it from http://selenium.seleniumhq.org/. It run directly in browser and it is platform independent and can be deployed on Linux, MAC and Windows environment (JavaScript-enabled Web browsers, such as recent versions of Microsoft Internet Explorer for Windows, Firefox, Mozilla, and Safari for Windows, Mac OS X, and Linux. )
Selenium IDE records and play for multiple browsers on multiple platforms.
The easiest way of getting started with selenium is to download Selenium IDE. You can download it form http://www.openqa.org/selenium-ide/ . It is an Integrated Development Environment(IDE) for test development and it ia a plug-in for firefox.
The test scripts can be recorded quite easily with its help. Apart from recorder the plug-in can be also used to run tests themselves, as well as for their debugging (using the option for executing the test step by step). The tests are recorded in HTML and table’s elements are used for describing the test-related data.
Selenium Remote Control(RC) allows you to write automated web application tests in any programming language against any HTTP website using any mainstream JavaScript-enabled browser.
Selenium Remote Control is actually uses remotely controlled server ( like a proxy server)
Selenium Core tests run directly in a browser, and simulates the real user. It runs in Internet Explorer, Mozilla and Firefox on Windows, Linux, and Macintosh. So it is a great tool for cross browser testing.

Thanks:

Wednesday, November 12, 2008

Wednesday, August 13, 2008

Web Application Testing Tricks


Web application is tested mainly for browser compatibility and operating system compatibility, error handling, static pages, back end load testing, user interface testing, Security testing, browser compatibility testing, and performance testing.
Browser Acceptance Testing:
Object is to make sure, application looks good and works as expected in all browser which is in scope of testing. Cross browser testing is about how your website looks across different browser and versions. How different browser Internet setting options makes difference on page, image and other object to load. Tester has to know about browser related problems, plus - ins, setting, options, video resolution and etc.
There are many tools to test browser compatibility. Such as HTML Validator from w3 school http://validator.w3.org/, form Adobe https://browserlab.adobe.com/index.html#.
Found bugs are all compatibility bug.
Before cross browser testing requirement should be clear about which browsers in scope of testing and which are not.

Security Testing:
It is all about trying to break security walls of web application. Trying to make an unauthorized access to data, application and information.
User id and password cracking - Trying to access user account by cracking log in and password, testing 'forgot your password' and its emails flow, trying to ckrak security answer. Multiple log in by same user from different computer and browser.
Session related : Copy session info id and try from another computer. copy url n paste in another browser, computer. Checking automated session expire is functionaly is there or not. If it is, it is as per configured in server.
Cookie related: Cookie should be deleted after session expired or browser closed. Persistent Cookies expires in configured times. C0rrupting, deleting cookie, and with different browser option.
Back and forward functionality (back button should be disable in may cases especially after some consent like terms and condition or e-sign)
Terms and conditions check
e-sign and validation numbers
Navigation hole do not exists: Such as there is no link to go certain page and edit user input. Users are not able to access sensitive information.
Privacy policy
encripted data passing :
Encryption encodes plain text into non-readable form providing privacy. Checking log files are sensitive data free. Web browsers will encrypt text automatically when connected to a secure server, evidenced by an address beginning with https.
User Authentication : based on user. like active directory.

SCRUM Process and role of a Tester

What is Scrum?
In software development world Scrum is one agile approach featuring an iterative process for managing a software development projects. Scrum is an iterative, team-based process especially suitable process to adopt for a rapidly changing requirement, or not clear requirement.
Agile Scrum has a structured way of development cycle and specific role of team member. A product development time is divided into a cycle called Sprint. A sprint is a period of time usually 2-4 weeks in length.
Daily stand up meeting: It allows team member to request more work, ask for help, and report completion of work. Basically three things are important - what you did yesterday, what you are going to do today and any question, for team. Or saying scrum terminologies, Tasks accomplished yesterday, task for today, and issues, ideas, helps, anything he may need or can offer to team.
What is Product Backlog Item (PBI)?
Product backlog is simply functional or technical requirement of a system or application created by product owner. In scrum process it is a unit of work that can be divided into multiple tasks called Sprint Backlog Item (SBI). Product Backlog Items may or may not contains detail information (usually not). Team member can add more detail in SBI. And product owner can add more detail later on too because PBI is a dynamic entity (usually add detail information for a early estimated effort). Usually, Sprint starts PBI includes very high level and as sprint progress, product owner add detail in existing one and new one targeting for coming sprint.
During Sprint planning, a meeting "Product Backlog Walkthrough" the SME and Product Owner will their vision of the system using the Product Backlog Items. The Product Owner presents the highest priority PBI to team. They collaborate about how much can be turned into an increment of potentially shippable product functionality during the next Sprint.
Sprint Backlog Item (SBI):
SBI simply is a task to be complete in a sprint. SBI is associated to a PBI, and relation is like parent and child. One PBI have one or more SBIs. SBIs remains unchanged during a sprint. So SBI is a tasks having 4-16 hrs (some company says not more than 8 hrs) estimated. Once, task is done its owner put estimated hour o and status to done.
User Stories:
User story is describes high level business flow, functionalities. It is a written description of story
......continue

Tuesday, August 12, 2008

Team Foundation Server - Simple Introduction for a tester

It is a tool from Microsoft for overall project collaboration. It has almost everything for a software development project such as source control, reporting, bug and requirement tracking, and team build.
Before further talking about TFS let spend some time understanding following:
WhAT Is Visual Studio Team System?
VSTS: MS- Visual Studio Team System is a powerful tool that integrates the entire team across the entire life cycle. It has solution to successfully, plan, build, deploy and test a project. According to Microsoft Visual Studio 2005 Team System is a productive, integrated, and extensible suite of life cycle tools that expands the Visual Studio product line to enable greater communication and collaboration among software development teams.
VSTS is divided in Integration, Architecture, Development and Testing according to different team's requirements. In general, It is designed in such a way that all stakeholders can directly communicate with each other, can view each others tasks and updates. So simply saying, it is a tool by Microsoft that provides guidance and communicates which item need to be worked on. And can customize it which ever methodology you follow. VSTS has two software development best practice methodologies.

1.1 One is MS Solution Framework for agile software development, it is recommended and default methodology form team system. It is best for team for more rapid, ready for change environment with communication with customer and project having small team. Agile is targeted to smaller team members on team. Team system is also highly follow the philosophy, model introduced by agile alliance:
-  individual interaction is more important than process and tool. 
-  Customer collaboration is highly fruitful for project than customer contracts.
- Responding to change according to situation makes positive impact on project rather than following plans.
1.2 Another is MSF for CMMI: CMMI is about process improvement which appeals to larger projects, typically project with long- range planning and communication are more important rather than frequent release and feedback form customer. CMMI is a model for continuous process development. It is targeted to reduced SDLC cycle times, improved ability to meet cost and schedule target and improve quality. It is a very formal methodology for SW development and used for environment where team needs close communications and integrated work environment. Project management – create and manage team project Work item tracking: Create and track bug, Tasks, Change management – version control management to project. Build server – build management Continuous Integration Build (CIB) Project site – SharePoint Reporting – different reporting chart can be customized.
From a Tester's point of view, if someone is going to join a team which is using VSTS/TFS, understanding team project's structure will make his job easy.
A team project has 5 main elements. Work Items, Documents, Reports, Team Build, and Source control.


A Work Item is means the work to be completed on the project. It can be a bug, a task for adding new feature, writing a business document etc. And can be created by anybody involved in.
Using document feature, once cad add project related document under document node.
Reports node is for project status tracking, for example a bug report, daily status report.
Team build node contains team builds, one can add new team build. Source Control node , by this one can access source codes.
So, in conclusion TFS glues the whole project team and facilitates to collaborate between the various team members/roles. VSTS Test edition is for testing purpose(automation). But all are integrated in visual studio environment.

Friday, August 8, 2008

Importance of Software Testing Theory

Every organization system operates under certain quality requirement. Software testing in an integral part of quality assurance and a tester can contribute to quality improvement by finding bug. A QA Analyst's responsibility is different then a tester's this role is responsible to create and in force standards and methods to improve overall software development and testing process.
Technical excellence (person who is very good at finding system bugs, good at automation tools, scripting, and debugging) is not enough to be a good software QA tester. Knowledge about qa methodology and process is equally important to use that technical ability. At the requirement gathering and analysis phase some QA persons cannot understand what their role is in this phase of SDLC. Their understanding is that there is nothing to test now because no test cases are ready yet. But, a QA person has a big role to play to check standards of the requirements itself.

What I personally feel is if a QA tester is clear about QA methodology, standards, his thinking is not based only on the documents but he also questions himself what are they going to develop? What is there in documents? What is missing? What is not necessary? This questioning process takes his knowledge to mature level which reflects in his documentation, test case writing, and his overall performance in other phases of STLC.

It is equally important for job search and interview. Question like 'when to start testing' is not that bad for a person who has drilled little bit QA methodologies. But I doubt it would that easy and to-the-point if a person doesn’t have methodological base. Sometime even software terms and terminologies put you in embracing situation during interview and during real work environment. Years back, my TL assigned me to walk new person through about project and testing. I spent significant effort to make him understand bug life cycle. He was actually testing bugs that were assigned to developers and not done. Here my intention is not to criticize him, but trying to tell that a tester person having knowledge of Bug life cycle and status would never touch a bug with 'not done' status and assigned to a developer. For more software testing theory topics go here

Wednesday, August 6, 2008

Basic QTP Interview questions

· What is Quick Test Professional (QTP)?
QTP is a testing tool used for regression and functional testing of an application. QTP provided by Mercury (now HP) is an interactive automation tool with feature "Record & Playback".
· What is object repository?
Object Repository is a repository to store objects of a component in current action in a tree view. All the information about the objects in your test is stored in object repository. There are two types of object Repositories.
· What is Descriptive programming?
QTP cannot take action on an object until unless its object description is in the Object Repository. But descriptive programming provides a way to perform action on objects which are not in Object repository
.

Monday, August 4, 2008

Quick Test Professional(QTP)- Useful Tricks

1. How to create a new action?
-Open QTP
-Insert>call to new action>start recording to create an action
-make sure to check “Reusable action”
-Save it in the QC folder where you can remember

2. How to call an existing action for the existing scripts?
-Open QTP
-Insert>Call to existing Action
-save the called action

3. How to insert “Wait” command in scripts?
Browser("Welcome to the Config").Page("Edit Name_2").WebList("FamilyList").Select "ISE 1.0"
Wait (6)
Browser("Welcome to the Config ").Page("Edit Name_2").WebList("moduleSelect").Exist

4. ReportEvent: With “If-Then-Else” logics
If Browser("Welcome to the Config ").Page("Welcome to the Config ").Link("General").Exist then
Reporter.ReportEvent micPass,"web element","general present"
else
Reporter.ReportEvent micFail,"webelement","General not present"
End if
Browser("Welcome to the Config ").Page("Welcome to the Config ").Link("General").Click

Note: make a copy of your original one line script and replace “Click” with “Exist then” in the copied one.
Click return key and type reporter. And you will see bunch of report events. Select ReportEvent and hit space bar to provide space. You will see bunch of other pop up list. Select “micPass” and provide a comma to it. Afterward put comments and status results inside the double quotes i.e. reporter.ReportEvent micFail,"webelement","general not present". You can see this report in test results.

5. Insert Standard Check Points while recording
If your test case is asking to “delete template”, then when you hit “delete” you will see some kind of confirmation message to make sure the template has been deleted. Put the check point when you see the confirmation message. To insert checkpoints while recording, for instance you want to insert checkpoint for “Confirmation message” and you’ve have not stopped recording yet after clicking “delete”, then in QTP, select insert>checkpoint>standard checkpoint>select the delete confirmation message. Done

6. GetRoProperty:
i.e. if you would like to get properties/value of an object
autofilltext=Browser("Config + Template Editor").Page("Config + Template Editor").WebElement("source_field_name").GetROProperty ("innertext")
msgbox autofilltext
If autofilltext="Velocity Template" Then
Reporter.ReportEvent 0,"Verify the 'Velocity template' box.","successfully identified Velocity template"
Else
Reporter.ReportEvent 1,"Verify the 'Velocity template' box.","Unable to identify Velocity template"
End If

You can give meaningful word to variable autofilltext for message box. Remove any operation i.e. Click right after dot at the end and replace it with GetRoProperty. To get the property of the object whether or not it is innertext or outertext, follow these steps. From QTP select ‘Object Spy’ and point it to the object you want to find its property and click the object. Once the object is clicked, property & values are saved in the Object Spy. Scroll down in the object spy window. You will see whether or not it is innertext or outertext. You can copy and paste it inside the parenthesis right after GetRoProperty.
And type msgbox
In if statement, value after assignment sign is the name of the object. Others are ReportEvent that we talked in Question 5

Note: usually you do not need to show message pop up if you’re running multiple test cases at night as when it pops up, it will stop other test cases to run until you click the pop up. So always comment it out for msgbox i.e. ‘msgbox autofilltext

7. Inserting Breakpoints
Usually break point are good when you don’t want to run whole script but upto some linke of the script.
If you point your mouse to the left side of the screen right next to your script and click to a particular line of the script, you will see big red dot. This is what called break point. Test run will stop to the point where you’ve placed your break point. This is easy tool specially when you’re are creating/testing/debugging scripts.
You can remove break point by clicking at the red dot.

8.How to FireEvent: Script for ‘Double-click’ ?
If you can not record for double clicking some object, you can generate a script for it. Here you got following script
Browser("Config + Template Editor").Page("Welcome to the Config ").WebButton("ABCD").Click
Now make it a double click action. Remove Click and type FireEvent, you will see popup with FireEvent and select it and inside double quotes, type “ondblclick” like the following
Browser("Config + Template Editor").Page("Welcome to the Config ").WebButton("ABCD").FireEvent"ondblclick"

9. How to use of the Data Table ?
Example script: Browser("Browser").Page("abc").WebEdit("USER").Set "ssharma"
a) Parameterization
simply provide multiple data in the same column. If these test data are valid, they qtp will run as many time as you have data
From QTP, Keyword Veiw>Select a value from the value column>click a parameter sign>Parameter>Give the object name in the name field such as USER from above example script. Now it will generate a column in the Global data table.

b) Tracking object values which can be replaced in the latter releases if data is deleted for some reason: from above example if you record a column in the
data table for USER (columnname) and data (ssharma), you can change value ‘ssharma to skhanal 

 10. how to use code/script to call an Excel Sheet?
Create a reusable action and type the following code:
Datatable.addsheet("login")
DataTable.Importsheet ( pathfinder.Locate( "[QualityCenter] Subject\Auto STD Regression Config+\login_info.xls")),"login","login"
For i = 0 to DataTable.GetSheet("login").GetRowCount -1
call Login(DataTable.Value("username", "login"), DataTable.Value("password","login"), DataTable.Value("url","login"))
datatable.Value("Result")="pass"
Next
DataTable.DeleteSheet("login")

11.How to make local object to globally available?
For Local Object Repository:
-Open the test on the QTP editor (Expert View)
-Resource>Object Repository
For Global Object Repository:
-Open the test on the QTP editor (Expert View)
-Resource>Object Repository Manager
You need to have both windows opened and simply drag and drop from local to global.
Once you move to global make sure to save it in the global repository.

12. How to export /import excel sheet?
User can make an Excel sheet with the required parameters and can import it to QTP when necessary. Ater creating excel sheet,open QTP, right click on any of the cells in the Data Table
File>Import.
a window pop-up box appears whether you will want to replace the contents of the current data table with the ones in the excel sheet.
Click OK .



Same way you can export data table into an external excel file. It is useful to use the required parameters in some different test run within QTP.
Or use script - Datatable.Export("path of file")

13. GetItem(1)
getItem(1) function will pick first values in the picklist If Browser("Welcome to the Config").Page("Welcome to the Config ").WebList("FamilyList").Exist Then Browser("Welcome to the Config ").Page("Welcome to the Config ").WebList("FamilyList").GetItem(1) Browser("Welcome to the Config ").Page("Welcome to the Config ").WebList("FamilyList").Select DataTable("FamilyList", dtGlobalSheet) End if

Friday, August 1, 2008

Fundamental of Web - Technologies, Protocols and More

Basic knowledge about web helps a tester lot be a good Web Tester. We everyday browse many web pages but we hardly looks how they are created.
The World Wide Web is a way of exchanging information between computers on the Internet

Many technologies, protocols, servers and other components are involved to develop a Web application.

Web Development Technologies protocols and servers: 

ASP.NET:
ASP.NET; a part of the .NET Framework, can be used to create anything from small, personal websites through to large, enterprise-class web applications. Languages Visual Basic, C#, JScript .NET, and J# can be used to develop (or language compatible with common language runtime).ASP.NET Web pages are completely object-oriented. Within ASP.NET Web pages you can work with HTML elements using properties, methods, and events.

Proxy Server:

  In an enterprise that uses the Internet, a proxy server is a server that acts as an intermediary between a workstation user and the Internet so that the enterprise can ensure security, administrative control, and caching service. A proxy server receives a request for an Internet service (such as a Web page request) from a user. If it passes filtering requirements, the proxy server, assuming it is also a cache server , looks in its local cache of previously downloaded Web pages. If it finds the page, it returns it to the user without needing to forward the request to the Internet. If the page is not in the cache, the proxy server, acting as a client on behalf of the user, uses one of its own IP addresses to request the page from the server out on the Internet. When the page is returned, the proxy server relates it to the original request and forwards it on to the user. To the user, the proxy server is invisible; all Internet requests and returned responses appear to be directly with the addressed Internet server.

Cache:
A cache is a french word meaning 'to store'. It is useful for to make page load faster, to reduce wide area bandwidth usage, to reduce the load placed in origin server. Negative side is it might return out-of - date information to a user. Sometime cache may not be able to reach server to return data

What web protocol is ?
When two or more computers communicate in Internet , they must have a common way in which to communicate. They use protocol to do it. Simply, protocol is an agreement by which two or more computers can communicate.
TCP/IP
Transmission Control Protocol/Internet Protocol(TCP/IP) is set of Internet communication protocol.
Transfer Control Protocol (TCP) breaks data into small pieces (called Packets) of no bigger than 1500 characters each. Each packet is inserted into different Internet Protocol (IP) “envelopes.” Each contains the address of the intended recipient and has the exact same header as all other envelopes. A router receives the packets and then determines the most efficient way to send the packets to the recipient. Upon arrival at their destination, TCP checks the data for corruption against the header included in each packet. If TCP finds a bad packet, it sends a request that the packet be re-transmitted. Numeric IP address( is a 32-bit address comprised of four 8-bit numbers (28) separated by periods. Each of the four numbers has a value between 0 and 255) works perfectly for web address However instead of IP Address, use of
Uniform Resource Locators (URLs) is in use because of it's user friendliness. So when a human types a URL into a browser, the request is sent to a Domain Name Server (DNS), which then translates the URL to an IP address understood by computers.



SMTP:
Simple Mail Transport Protocol (SMTP) is the network protocol used to send email across the Internet. the messages can then be retrieved with an e-mail client using either POP or IMAP (POP - Post Office Protocol, and IMAP - Internet Message Access Protocol are protocols to retrieve e-mail from server) .

HTTP/HTTPS :
HTTP (Hypertext Transfer Protocol) is the set of rules for transferring files (text, graphic images, sound, video, and other multimedia files) on the World Wide Web. Whenever you surf the web, your browser will be sending HTTP request messages for HTML pages, images, scripts and styles sheets. Web servers handle these requests by returning response messages that contain the requested resource.
HTTP protocol is not suitable for use in a wide range of applications because it can be easily monitored and replayed. For example, someone using a network monitor can easily capture passwords used to access a banking web site. So, HTTP supports the use of several authentication mechanisms to control access to pages and other resources. HTTPs runs over an encrypted SSL session (HTTP over SSL (Secure Sockets Layer)) . So, if the website begins with https:// instead of http://, it is a secure site. Client and server need to create a shared secret key by using a public / private key handshake. Typically, HTTP data is sent over TCP/IP port 80, whereas SSL HTTP data is sent over port 443.
Web have a secure connection or not:
In Internet Explorer, you will see a lock icon in the Security Status bar. The Security Status bar is located on the right side of the Address bar.
For example this web site is not secure. Security Status bar color is red. and there is certification error instead of lock sign.


This website is secured. It has white Security Status bar That means it has normal validation certificate and lock sign is there.

This website is secured. it has green Security Status bar . That means it has extended validation certificate.


Color in web status bar; What it means?
Red
The certificate is out of date, invalid, or has an error. For more information, see "About Certificate Errors" in Related Topics.
Yellow
The authenticity of the certificate or certification authority that issued it cannot be verified. This might indicate a problem with the certification authority's website.
White
The certificate has normal validation. This means that communication between your browser and the website is encrypted. The certification authority makes no assertion about the business practices of the website.
Green
The certificate uses extended validation. This means that communication between your browser and website is encrypted and that the certification authority has confirmed the website is owned or operated by a business that is legally organized under the jurisdiction shown in the certificate and on the Security Status bar. The certification authority makes no assertion about the business practices of the website.

FTP:
File Transfer Protocol (FTP), a standard Internet protocol is the simplest way to exchange files between computers on the Internet. Like the Hypertext Transfer Protocol HTTP which transfers displayable Web pages and related files, and the Simple Mail Transfer Protocol SMTP which transfers e-mail, FTP is an application protocol that uses the Internet's TCP/IP protocols. FTP is commonly used to transfer Web page files from their creator to the computer that acts as their server for everyone on the Internet. It's also commonly used to download programs and other files to your computer from other servers.

DHCP:
Dynamic Host Configuration Protocol (DHCP) is a standard protocol defined by RFC 1541 (which is superseded by RFC 2131) that allows a server to dynamically distribute IP addressing and configuration information to clients. Normally the DHCP server provides the client with at least this basic information: •IP Address,•Subnet Mask,•Default Gateway. Other information can be provided as well, such as Domain Name Service (DNS) server addresses and Windows Internet Name Service (WINS) server addresses. The system administrator configures the DHCP server with the options that are parsed out to the client.


Session :
Session management entails the application sending the client (in most cases, a web browser) a session token after successful authentication. In most cases, this token is passed via the Set-Cookie directive of HTTP and is stored on the client. The session token must then be sent by the client along with every HTTP request to the server to identify itself to the web-based application. The application can then determine whether the client is authorized to access the page being requested.
once a user has authenticated herself to the web server, her next HTTP request (GET or POST) should not cause the web server to ask her for her account and password again. For a discussion of the methods used to accomplish this please see HTTP cookie.
The session information is stored on the web server using the session identifier (session ID) generated as a result of the first (sometimes the first authenticated) request from the end user running a web browser. Web server stores session IDs and the associated session data (user name, account number, etc.).
A cookie is a piece of data that is issued by a server in an HTTP response and stored for future use by the HTTP client. The client then re-supplies the cookie value in subsequent requests to the same server. This mechanism allows the server to store user preferences and identity individual users. Cookies are usually used to represent or reference private information.

Bug Classification - Severity, Priority and Triage

Severity is about the technical impact of a defect. Priority is about the urgency of the fix. Important is that severity is one of the factors influencing priority and that only priority should be used to decide what to fix next . For example, your project may have a policy to fix higher priority bugs p1 before fixing lower (p2 to 4); or to block the release of a product that has open, unfixed p1 bugs; or even require that a p1 bug be fixed immediately (in 4 hours, or the next patch) if it was found in a released, live product. The Severity of open bugs is often used to measure the overall quality of the product, or of a particular feature. Understandably, many projects use bug severity, along with other project or user data, to determine the priority of fixing a bug.

Severity
Sev 1 - System/Application crash, or data loss. Product/Service instability, major test blockage, broken build or failed new build
Sev 2 - Major loss of functionality or other severe problems (feature unusable; product crashes in obscure cases), Bug in major feature with complex workaround, or moderate test blockage.
Sev 3 - Minor functionality and feature problems; may affect 'fit and finish'. Feature problem with simple workaround, or small test impact.
Sev 4 - Very minor problem such as misspelled words (typos), unclear wording or error messages in low visibility fields, incorrect tab order in GUI, obscure feature broken, etc. Little or no test impact.

Priority
P1 - Fix by next build.
P2 - Should Fix soon, (specific timing based on test/customer “cost” of workaround, if exists.)
P3 - Fix (to replace customer workaround by next project milestone with related deliverable. )
P4 - Consider fix by upcoming release (somewhat trivial ticket, but may be postponed.)

Bug meeting - Triage:
Bug Triage Meeting is project meeting where software developer, software tester and business owner are the participants.
In most of the projects I worked, a bug triage meeting, is usually facilitated by test team lead. Triage team steps through each bug one at a time, reviewing about bug's severity, priority, and its impacts on development, test and business.

Monday, July 28, 2008

Bug Life Cycle - BLC




Bug life cycle starts when a bug is found by a tester. After that a tester has to do several things in different point of times.
The very first things to do before logging a bug is to make sure that this issue has already been identified or not. Simply, searching on bug storing database for similar issue. If bug is already has been entered; make sure it is still active and scenario is same that you have identified. If not reopen it and add more information (if repro. steps are different add your ) and bring this issue to developer's/team's attention.
Always avoid entering duplicate bug. Adding duplicate bug effects a tester image .
After tester entering a bug it must be assigned to someone, mostly to developer. (Eventually goes to developer). Developer checks bug and then fixes his code in same build, produces a new build with fix and assign bus to tester to verify it. Now tester needs to verify the fix, which is called regression testing. If bug has been fixed, it is tester's responsibility to close it. If not, the bug will be reactivated and cycle will starts all over again.


Monday, July 21, 2008

Scripting

HTML:
Hyper Text Markup Language :HTML file generally contains two soft of information - 1. markup is a method of telling a web browser how to display a page. 2. content this is the information you actually want to display. HTML is very easy to learn. Please go to the link Here and Here to learn about HTML in detail.

XML:
Extensible Markup Language (XML) allows its users to define their own elements. XML and HTML both contains markup symbols and contents. But XML describes the content in terms of what data is being described. XML uses tag to describe the data. Its primary purpose is to facilitate the sharing of structured data across different information systems.
XML document is a collection of data. In other words it does’t make much difference between the other files that store data. A XML in a database format is a self describing, portable, and can describe data in tree or graph structure. XML is a sort of Database Management System (DBMS).
(....more about XML from testing perspective on qa-advance. I will talk about XML from Web technology perspectives, XML validation and more . But later )

VB Scripting:
VB scripting is a light version of Microsoft's programming language Visual Basic. An automation tester must know VB scripting. Basic testing by recording and play back is not enough in real testing world. Script enhancement and debugging is must necessary. Rational Functional Tester (.NET Version), Quick Test Professional, Test partner and others widely used automation tools record script in VB scripting. So, if you have VB scripting knowledge your job will be very easy.
Please browse Here. to learn VB scripting . More in future after talking about automation framework, i will talk about VB scripting from testing perspective.

Friday, July 18, 2008

Some Useful UNIX Commands for a QA Tester

In a UNIX environment, a tester frequently involves in -
Running scripts as per test case step requirement.Bulleted ListFile
manipulation (copying/renaming/deleting)
Navigation (change directory/listing
files/dictionary)
File directory creating
Monitoring
remote log in
Using VI/others editors
Search command "grep"

grep
This command is used to search for information in file/files. Suppose that we have a file restless whose contents are
seafood list fish
warm fish
file
enter
same
fish
list three two one
lost
ashley
list same thins again
ok
bye bye
ok tata

Use ‘grep’ commands

Command:
grep fish restless

Result:
seafood list fish
warm fish
fish

Command:
grep enter restless

Result:
enter

Command:
grep ola restless

Result: No output was returned because "ola" is not in file.

‘grep’ can be combined with other command as well with the help of pipe. grep can be combined
with sort command to put out in a alphabetical order. Let’s see

Command:
grep fish restless sort

Result:
seafood list fish
fish
warm fish

Use ‘man grep’ command to learn more about ‘grep’

Wednesday, July 9, 2008

Useful protocols for a software tester

What web protocol is ?
When two or more computers communicate in Internet , they must have a common way in which to communicate. They use protocol to do it. Simply, protocol is an agreement by which two or more computers can communicate.


TCP/IP : 
Transmission Control Protocol/Internet Protocol(TCP/IP) is set of Internet communication protocol. Transfer Control Protocol (TCP) breaks data into small pieces (called Packets) of no bigger than 1500 characters each. Each packet is inserted into different Internet Protocol (IP) “envelopes.” Each contains the address of the intended recipient and has the exact same header as all other envelopes. A router receives the packets and then determines the most efficient way to send the packets to the recipient. Upon arrival at their destination, TCP checks the data for corruption against the header included in each packet. If TCP finds a bad packet, it sends a request that the packet be re-transmitted. Numeric IP address( is a 32-bit address comprised of four 8-bit numbers (28) separated by periods. Each of the four numbers has a value between 0 and 255) works perfectly for web address However instead of IP Address, use of Uniform Resource Locator's (URLs) is in use because of it's user friendliness. So when a human types a URL into a browser, the request is sent to a Domain Name Server (DNS), which then translates the URL to an IP address understood by computers.

HTTP/HTTPS :
HTTP (Hypertext Transfer Protocol) is the set of rules for transferring files (text, graphic images, sound, video, and other multimedia files) on the World Wide Web. Whenever you surf the web, your browser will be sending HTTP request messages for HTML pages, images, scripts and styles sheets. Web servers handle these requests by returning response messages that contain the requested resource.
HTTP protocol is not suitable for use in a wide range of applications because it can be easily monitored and replayed. For example, someone using a network monitor can easily capture passwords used to access a banking web site. So, HTTP supports the use of several authentication mechanisms to control access to pages and other resources. HTTPs runs over an encrypted SSL session (HTTP over SSL (Secure Sockets Layer)) . So, if the website begins with https:// instead of http://, it is a secure site. Client and server need to create a shared secret key by using a public / private key handshake. Typically, HTTP data is sent over TCP/IP port 80, whereas SSL HTTP data is sent over port 443.
Web have a secure connection or not:
In Internet Explorer, you will see a lock icon in the Security Status bar. The Security Status bar is located on the right side of the Address bar. For example this web site is not secure. Security Status bar color is red. and there is certification error instead of lock sign.

This website is secured. It has white Security Status bar That means it has normal validation certificate and lock sign is there.

This website is secured. it has green Security Status bar . That means it has extended validation certificate.
Color in web status bar; What it means? Red The certificate is out of date, invalid, or has an error. For more information, see "About Certificate Errors" in Related Topics. Yellow The authenticity of the certificate or certification authority that issued it cannot be verified. This might indicate a problem with the certification authority's website. White The certificate has normal validation. This means that communication between your browser and the website is encrypted. The certification authority makes no assertion about the business practices of the website. Green The certificate uses extended validation. This means that communication between your browser and website is encrypted and that the certification authority has confirmed the website is owned or operated by a business that is legally organized under the jurisdiction shown in the certificate and on the Security Status bar. The certification authority makes no assertion about the business practices of the website.

FTP: 
File Transfer Protocol (FTP), a standard Internet protocol is the simplest way to exchange files between computers on the Internet. Like the Hypertext Transfer Protocol HTTP which transfers displayable Web pages and related files, and the Simple Mail Transfer Protocol SMTP which transfers e-mail, FTP is an application protocol that uses the Internet's TCP/IP protocols. FTP is commonly used to transfer Web page files from their creator to the computer that acts as their server for everyone on the Internet. It's also commonly used to download programs and other files to your computer from other servers.

SOAP:
Simple Object Access Protocol (SOAP) is a protocol that can be used for accessing the Web pages. SOAP is an XML based Object invocation Protocol. SOAP was developed for distributed applications to communicate through HTTP and firewalls. SOAP messages are independent of any operating system or protocol and may be transported using a variety of Internet protocols including SMTP, MIME, and HTTP 
SMTP:
Simple Mail Transfer Protocol, a protocol for sending email messages between servers. The messages can then be retrieved with an e-mail client using either POP or IMAP

POP: Post Office Protocol, a protocol used to retrieve e-mail from a mail server to email client. POP stores your email on your computer in your email client (i.e. Thunderbird, Outlook, or whatever program you use to check email). When you check email, it is downloaded to your email client and removed from the mail server. This is why you can read your email when you're offline—because the email is actually on your computer you don't need an Internet connection to see it.

IMAP: It is a protocol for accessing mail that is in mail server using an email client. IMAP keeps your email on the mail server so you can access it from multiple locations and with multiple email clients. For example, you can see the same email at home and at work. Likewise, you can see it in iCampus, Webmail, and Thunderbird.

MIME: SMTP uses the MIME protocol to send binary data across TCP/IP networks. The MIME protocol converts binary data to pure text.

TCP: TCP (a network protocols) is used for transmission of data from an application to the network. TCP is responsible for breaking data down into IP packets before they are sent, and for assembling the packets when they arrive. IP is responsible for the sending and receiving data packets over the Internet.

DCHP: Is responsible for allocating the dynamic IP address to computer in a network. Dynamic Host Configuration Protocol (DHCP) is a standard protocol defined by RFC 1541 (which is superseded by RFC 2131) that allows a server to dynamically distribute IP addressing and configuration information to clients. Normally the DHCP server provides the client with at least this basic information: •IP Address,•Subnet Mask,•Default Gateway. Other information can be provided as well, such as Domain Name Service (DNS) server addresses and Windows Internet Name Service (WINS) server addresses. The system administrator configures the DHCP server with the options that are parsed out to the client.

HTTP
Hyper Text Transfer Protocol HTTP takes care of the communication between a web server and a web browser. HTTP is used for sending requests from a web client (a browser) to a web server, returning web content (web pages) from the server back to the client. HTTPs run over an encrypted SSL session (HTTP over SSL (Secure Sockets Layer)). So, if the website begins with https:// instead of http://, it is a secure site. Client and server need to create a shared secret key by using a public / private key handshake. Typically, HTTP data is sent over TCP/IP port 80, whereas SSL HTTP data is sent over port 443.
FTP - FTP refers to a network protocol responsible for transferring files from one computer to another on the Internet. The FTP service is provided through a TCP network protocol. In order to establish an FTP connection the user needs to point his FTP client to an FTP server. The information needed includes an FTP host, FTP account credentials (username or password) and a FTP port. The default command port for FTP connections is port 21.

ICMP - Internet Control Message Protocol takes care of error-handling in the network. It is chiefly used by networked computers' operating systems to send error messages—indicating, for instance, that a requested service is not available or that a host or router could not be reached

SNMP - Simple Network Management Protocol. It is used mostly in network management systems to monitor network-attached devices for conditions that warrant administrative attention

Software Testing Techniques

Testing Techniques can be divided into following

Specification-based - black-box techniques
Structure-based - white-box techniques
Experience-based techniques


White-box techniques (Structure Based):
This is a software testing technique whereby explicit knowledge of the internal workings of the item being tested is used to select the test data. Unlike black box testing, white box testing uses specific knowledge of programming code to examine outputs. The tests written based on the white box testing strategy incorporate coverage of the code written, branches, paths, statements and internal logic of the code etc.
Usually Unit testing, component testing are the white-box testing. But  it is equally important in integration level as well to verify one module calls another module in a right way.
Structural testing has well defined way of testing. which are defined as -


Statement Testing: It is a component level testing and tests single statements.
Loop Testing: Propose of loop testing is to validating loop constructs. Usually tests-loop to be skipped, loop to be executed more than once, loop to be executed just once
Path Testing: will discuss later
Condition/Branch Testing:  Validating all possible output in specific condition. For every decision, each branch need to be executede at least once. IF, for while, Switch

IF ( a = b) THEN
    Statement 1
ELSE
    statement 2
END IF






Experience-based techniques:
Experienced-based testing is where tests are derived from the tester’s skill and intuition and their experience with similar applications and technologies. it is useful in identifying special tests not easily captured by formal techniques, especially when applied after more formal approaches.
A commonly used experienced-based technique is error guessing. Generally testers anticipate defects based on experience.

Black-Box  (Specification based):
Testing software based on output requirements and without any knowledge of the internal structure or coding in the program.

Techniques:
Equivalent Partitioning
Boundary Value Analysis
State Transition Testing
Cause- Effect Graphing
Syntax Testing
Use case testing
Equivalence partitioning (EP) is a test case design technique that is based on the premise that the inputs and outputs of a component can be partitioned into classes that, according to the component's specification, will be treated similarly by the component.. Thus the result of testing a single value from an equivalence partition is considered representative of the complete partition.As an example consider any program that accepts days of ht week and months of they year as inputs. Intuitively you would probably not expect to have to test every date of the year. You would obviously try months with 30 days (e.g. June) and months with 31 days (e.g. January) and you may even remember to try out the special case of February for both non-leap year (28 days) and leap years (29 days). Equally, looking at the days of the week you would not, depending on the application, test every day. You may test for weekdays (e.g. Tuesday) and weekends (e.g. Sunday). What you are in effect doing is deciding on equivalence classes for the set of data in question.Not everyone will necessarily pick the same equivalence classes; there is some subjectivity involved. But the basic assumption you are making is that anyone value from the equivalence, class, is as good as any other when we come to design the test.We hope that you can see how this technique can dramatically reduce the number of tests that you may have for a particular software component.

Boundary Value Analysis is base on the following premise. Firstly, the inputs and outputs of a component can be partitioned into classes that, according to the component's specification, will be treated similarly by the component and, secondly, that developers are prone to marking errors in their treatment of the boundaries of these classes. Thus test cases are generated to exercise these boundaries.State transition testing focuses on the testing of transitions from one state (e.g., open, closed) of an object (e.g., an account) to another state.
A cause-effect graph is a graphical representation of inputs (causes) with their associated outputs (effects), which can be used to design test cases. Furthermore, cause-effect graphs contain directed arcs that represent logical relationships between causes and effects. Each arc can be influenced by Boolean operators. Such graphs can be used to design test cases, which can directly be derived from the graph or to visualize and measure the completeness and the clearness of a test model for the tester.
Syntax Based Testing is a techniques in which syntax command generator generates test cases based on the syntax rules of a system. Every input has a syntax. Both valid and invalid values are created. It is a data-driven black-box testing techniques for testing input data to language processor, such as string processor and compilers. test Cases are based on rigid data definition.
Test execution automation is essential for syntax testing because this method produces a large number of tests.
Use case testing
Decision table testing: Decision tables are a good way to capture system requirements that contain logical conditions, and to document internal system design. They may be used to record complex business rules that as system is to implement. The specification is analyzed, and conditions and actions of the system are identified. The input conditions and actions are most often stated in such a way that they can either be true or false (Boolean). The decision table contains the triggering conditions, often combination of true and false for all input conditions, and the resulting actions for each combination of conditions. Each column of the table corresponds to a business rule that defines a unique combination of conditions, which result in the execution of the actions associated with that rule. The coverage standard commonly used with decision table testing is to have at least one test per column, which typically involves covering all combination of triggering conditions.

Wednesday, June 4, 2008

Test Planning and Writing a Test Plan

Test planning is the activities of identifying and designing the testing process.  The planning phase provides an opportunity for the tester to determine what to test and how to test it. Creating a Master Test Plan is the best way to do it and is a major output of test planning.
Test Plan is the most important ongoing document which is created by QA team and helps to manage test project.
Test Planning is one of the MUST have skill for a software tester, including the selection of techniques and methods to be used to validate the product against its approved requirements and design. Test planning assesses the business and technical risks of the software application, and then develops a plan to determine if the software minimizes those risks. Test planners must understand the development methods and environment to effectively plan for testing. Test plan generally includes:

Test Scope – what is to be tested 
Requirements/Traceability – defines the tests needed and relates those tests to the requirements to be validated.
Estimating – determines the amount of resources and time frames required to accomplish the planned activities.
Scheduling – establishes milestones for completing the testing effort and their dependencies on meeting the rest of the schedule.
Staffing selecting the size and competency of staff needed to achieve the test plan objectives.
Test Approach methods, tools, coverage and techniques used to accomplish test objectives. 
Test Check Procedures (i.e., test quality control) – set of procedures based on the test plan and test design, incorporating test cases that ensure that tests are performed correctly and completely. 
Maximizing test Effectiveness – methods to assure test resources will be used most effectively.

Test Planning Steps:
Step 1. Build Test Plan:
Identified all those mentioned above, gather some ideas and then focus on writing the Test Plan.
1.1 Prepare Introduction
1.2 Define High level functional Approach
1.3 Identify types of test
1.4 Identify Exit Criteria
1.5 Establish regression testing strategy.
1.6 Organize Test team
1.7 Establish test environment
1.8 Define dependencies
1.9 Create Test Schedule
1.10 Select Test Tool
1.11 Establish defect tracking procedures
1.12 Establish change request procedures
1.13 Establish Version control procedures
1.14 Define Build configuration procedures
1.15 Establish reporting procedures
1.16 Define approval procedure


Step 2. Define metrics objectives:
2.1 Define Metrics
2.2 Define Metric points
Step 3. Review/Approve
3.1 Schedule/Conduct Review
3.2 Obtain approval

Tuesday, June 3, 2008

A tester need to know about Logical and Physical design..

Business requirements are defined during the requirement phase. It is followed by logical design and refines requirement. Logical design is an abstract, conceptual not physical.
Logical design is all about detail system framework and logical architecture is the manner in which logical components of a solution are organized and integrated. The Architectural Design phase, where a software architecture for the implementation of the requirements is designed and specified, identifying the components within the software and the relationships between the components.
Physical Design describes how an information system will be physically implemented in order to meet its logical requirements. This involves specifying the technical (hardware and software) components that will enable the logical design specifications to be implemented.
The logical design phase is verified with static techniques. for example one module may need a particular data created by another module is not provided correctly. Static anlaysis can be applied to detect these types of control flow errors.
Integration test cases is a good approach to test it and determine whether all components interface properly, parameters are passed, and the file processing is correct. It doesnot verify that functionality is correct, only it perfrm as it is designed,

Roll of a Tester in different phase of SDLC


Requirement Phase:
The testing process should begin early stage in application development cycle.
Testers need a solid understanding of the product so they can devise better and more complete test plans, designs, procedures, and cases. Early test-team involvement can eliminate confusion about functional behavior later in the project life cycle. In addition, early involvement allows the test team to learn over time which aspects of the application are the most critical to the end user and which are the highest-risk elements. This knowledge enables testers to focus on the most important critical and high priority part of application.
During the requirement phases of SDLC. the business requirements are defined on high level. During this phase a tester can come up with document testing approach to verify its quality, completeness, and correctness, can point out contradictory requirements.
More systematically, during the requirement phase, a tester can build a Acceptance Test Plan There are some formal approaches and documents which can be created during this phase. Such as:
Inspection/ Walkthrough:
System/Acceptance Test Plan:
Checklist:
Requirement Checklist:

Logical and Physical design..



Business requirment are defined during the requirment phase. It is followd by logical design and refines requirement. Logical design is an abstract, and it is conceptual not physical.
Logical design is al about detail system framework and Logical architecture is the manner in which logical components of a solution are organized and integrated. The Architectural Design phase, where a software architecture for thei mplementation of the requirements is designed and specified, identifying the components within the software and the relationships between the components.
Physical Design describes how an information system will be physically implemented in order to meet its logical requirements. This involves specifying the technical (hardware and software) components that will enable the logical design specifications to be implemented.
The logical design phase is verified with static techniques. for example one module may need a particular data created by another module is not provided correctly. Static anlaysis can be applied to detect these types of control flow errors.
Integration test cases is a good approach to test it and determine whether all components interface properly, parameters are passed, and the file processing is correct. It doesnot verify that functionality is correct, only it perfrm as it is designed,

Traceability matrix

What is it?
 
Traceability matrix can be made more elaborate by tracing the requirements to the design to the code to the test cases. In this way we can come to know which requirement change will affect which part of the design and which part of the code and the test case.Usually this is an excel sheet. Traceability matrix is one which tells the deviation in the current test process with the actual. A   requirement Traceability Matrix is a document that traces user requirements from analysis through implementation. It can be used as a completeness check to verify that all requirements are present or that there are no unnecessary/ extra feature.
At each step in development cycle, the requirements code and associated test cases are recorded to ensure that requirement is addressed in the final system. Both user and developer have ability to easily cross - reference the requirements to the design , programming, test cases.

Friday, May 30, 2008

Software Testing LifeCycle(STLC), V-MODEL



Software Test Life Cycle:

Software testing life cycle identifies what test activities to carry out to accomplish quality assurance process in a software development project.
There are different kinds of software development life cycle(SDLC) such as Waterfall, Spiral, Agile, and many others. Software testing has its own life cycle that intersects with every stage of the SDLC either it is Waterfall, Spiral or Agile. However, STLC varies from one to another based on size of project, test team, test in Scope/out of scope, and code release date (how frequently). So, knowledge about some of the major phase in STLC, quality assurance activities during phases and role of a tester, makes you as a tester always ready to accomplish your task with a mark. This picture describes one of widely used STLC phases.
Generally STLC for a single test cycle consists of phases: 1) Planning, 2) Analysis, 3) Design, 4) Initial Testing 5) Testing Cycles, 6) Final Testing and Implementation and 7) Post release
Planning :
  • High level test plan
  • Identify review process, Metrics
  • Bug reporting procedures
  • Acceptance criteria for QA
  • schedule
Analysis Phase:
  • Develop Test Case format , Validation Matrix
  • Develop, and plan Test Cycles matrices and time lines
  • Begin writing Test Cases based on Functional Validation matrix
  • Map baseline data to test cases to business requirements
  • Identify Automation, Manual and Types of testing ,
  • Test environment, automation system setup.
Design :
  • Test -plan(ning) review and verify.
  • Review matrix (coverage).
  • Continue working on Test Cases.(update, new )
  • Finalize test case selection for each cycle for manual run and automation.
Initial Testing
  • Complete all plans, Test Case, scripting
  • Unit test (Automated?)
Test Cycle:
  • Test Cycle 1, run first set of test
  • Report bugs - Triage(bug verification)- Bug fixes - Regression
  • Add test cases as required
  • Test Cycle 2, 3 ...
Final Testing and Implementation :
  • Code Freeze
  • Run Test cases for including performance level .
  • Communicate defect tracking metrics.
  • Regression
  • Documents.
Post Release
  • evaluation meeting - lesson learned
  • Prepare final Defect Report and metrics. Develop strategies to prevent similar problems in future project.
  • Milestones for improvements
  • Environment clean-up.clean (tag and archive tests and data for that release) restore test machines to baseline for next test cycle
------------------------------------------------------------------------------------------

V-model



Although variants of the V-model exist, a common type of V-model uses four test levels, corresponding to the four development levels. The four levels used in this syllabus are:
component (unit) testing;
integration testing;
system testing;
acceptance testing.
In practice, a V-model may have more, fewer or different levels of development and testing, depending on the project and the software product. For example, there may be component integration testing after component testing, and system integration testing after system testing. Software work products (such as business scenarios or use cases, requirements specifications, design documents and code) produced during development are often the basis of testing in one or more test levels. References for generic work products include Capability Maturity Model Integration (CMMI) or ‘Software life cycle processes’. Verification and validation (and early test design) can be carried out during the development of the software work product