- C#
- Java
- Groovy
- PHP
- Perl
- Python
- Ruby
etc.
- Windows
- Linux
- Macintosh
- Selenium
IDE
- Selenium
remote control
- Selenium
grid
Articles, comments, queries about the processes of Software Product Development, Software Testing Tutorial, Software Processes .
Posted by
Sunflower
at
1/02/2013 03:13:00 PM
0
comments
Labels: Automated, Automation, Development, Domain, Elements, Framework, Functionality, Languages, Platform, Portable, Selenium, Software testing, Test Scripting Language, Tests, TSL, Users, Web Applications, Web browser
![]() | Subscribe by Email |
|
Posted by
Sunflower
at
7/18/2012 11:40:00 AM
0
comments
Labels: Applications, Client, Client Server, Compatibility, Components, Cross platform, Differences, Distributed, Errors, GUI, Network, Platform, Servers, Tasks, Testers, Testing, Users, Web Applications, Web browsers
![]() | Subscribe by Email |
|
Posted by
Sunflower
at
7/11/2012 03:29:00 PM
0
comments
Labels: Development, End users, Functionality, Observer, Owner, Quality, Quality assurance, Site, Software testing, Team, Testers, Tests, Time, Usability, Web Applications, Website, Website Usability Testing, Websites
![]() | Subscribe by Email |
|
Posted by
Sunflower
at
5/02/2012 01:47:00 PM
1 comments
Labels: Application, Attackers, attacks, Bugs, Defects, Emphasize, Errors, Flaws, Internet, Methodology, Network, Penetration testing, Reliable, Security, Simulated, Software testing, Steps, Web Applications, Web sites
![]() | Subscribe by Email |
|
Posted by
Sunflower
at
4/20/2012 07:52:00 PM
0
comments
Labels: Attacker, attacks, Bugs, Commands, Data, Database, DBMS, Defects, Errors, Functionality, Functions, Injection, Input, Privilege Escalation, SQL injection, SQL injection attack, Statements, Users, Web Applications
![]() | Subscribe by Email |
|
XSS or cross site scripting is a much familiar word in today’s cyber world. Cross site scripting is categorized under the category of computer security vulnerabilities which are common among the web applications.
Posted by
Sunflower
at
4/17/2012 11:22:00 AM
0
comments
Labels: Access, Advantages, Attacker, Client, Content, Control, Cross site scripting, Data, Domain, Factors, Flaws, Limitations, Scripting, Security, Users, Web Applications, Web browser, Web pages, XSS
![]() | Subscribe by Email |
|
Today’s world is lot more dependent on the number of software applications which are involved with most of the tasks that we do. Application softwares are gaining popularity day by day by the name of “apps” and there are million application softwares available today and a lot others are in processing.
Many application softwares of different specifications and different designs under so many categories have been designed to enable the user to perform his/ her tasks efficient with ease and with reduced drudgery of performing many tasks that otherwise would have be carried out manually.
Some common examples of application softwares are:
1. Accounting softwares
2. Enterprise softwares
3. Graphics software
4. Media players
5. Office suites and so on.
There are so many types of application softwares like desktop application softwares, web application softwares, utilities and so on based on the field where they are used.
This article is focussed up on two main types of application softwares namely web application softwares and the desk top application softwares and the differences between them.
Posted by
Sunflower
at
4/08/2012 12:58:00 PM
0
comments
Labels: Application, Code, Design, Desktop Applications, Differences, Internet, Intranet, Languages, Offline, Online, Packages, Performance, Programming, Security, Tasks, Web Applications, Web browser
![]() | Subscribe by Email |
|
Most of the time while browsing the same over many browsers you might have noticed considerable differences between the displays across the various browsers. These differences cause a lot of annoyance to the users.
There are various reasons why there occur differences across the different browsers. This article is focussed up on such browser display differences and errors as well as suggestions to avoid them.
Posted by
Sunflower
at
3/16/2012 11:55:00 PM
0
comments
Labels: Browsers, Code, Debug, Debugging, Differences, Display, Errors, Factors, Goals, HTML, Incompatibility, Screen, Size, Tools, Users, Versions, Web Applications, Web browser, Web pages, Websites
![]() | Subscribe by Email |
|
It is a universal fact that every thing in this world is infected with some discrepancies. So does it hold well for the web browsers! This article is here to discuss about the bugs associated with the web browsers.
Till date so many bugs of the web browsers like Mozilla, internet explorer, Netscape, opera and so on have been discovered. Let us check out some of the prominent errors:
Posted by
Sunflower
at
3/15/2012 11:54:00 PM
0
comments
Labels: Browsers, Bugs, Challenges, Compatible, Defects, Design, Elements, Font, HTML, Keywords, Tables, Tags, Text format, Web Applications, Web browser, Web pages, Website
![]() | Subscribe by Email |
|
Malfunctioning of the web sites across various browsers has become a topic of utter annoyance.
Why it happens so that your web site functions perfectly well on one browser and at the same time fails to perform well in some other browser?
Why it appears to be missing some thing while it appears as proper on other browsers?
The root cause of all such errors and differences is the browser incompatibility.
WHAT IS BROWSER INCOMPATIBILITY & TOOLS FOR DETECTING BROWSER INCOMPATIBILITY
- There are various tools that can help you across detecting the browser incompatibility.
- Such tools check for the browser incompatibility by comparing the various snap shots of the web site operating under various web browsers.
- Different browsers and different browser versions all add up to the browser incompatibility.
- Browser incompatibility though cannot be eradicated fully; it can be at least reduced to a certain extent.
- Though the browser is only to be blamed for its incompatibility, the measures to reduce or avoid it can be taken from both sides.
- It can be done by improving either the standards of the browser or by taking care of the web site.
- If the web site in its design and code is good, incompatibility will be noticed less.
WHY INCOMPATIBILITY ARISES?
- It arises either because of the incompatibility of the web browser or because of the problems in the web site itself.
- So you need to focus on the design an implementation of your web site rather than bogging up yourself with the browser issues.
- Employing cutting edge HTML can also run you in to the incompatibility problems as the HTML standards usually are a way step ahead of what is supported by the web browsers.
- Till now, no such browser has been developed that will take in to consideration 100 percent HTML.
- No doubt there are certain browsers that are a bit close to this value than the others.
- Using latest versions and standards of the HTML is always not a good choice. So be wise when you choose the version of HTML for designing up your web site.
- Another fact to be kept in mind is that not all the web browsers are equally efficient in translating the HTML code in to formatted web sites.
- There are some browsers that may leave certain parts of the HTML code because they are not able to execute it and again you will have trouble with your browser compatibility.
- Also all the web browsers do not translate a web page in the same manner and don’t give the same results.
- Before you start building up your web site, check out the compatibility of the different browsers so that you will have an idea what all formats and standards they support and you can build your site according and simultaneously avoiding a bug deal of incompatibility.
- After you have finished developing your web site, have your pages validated. If you are getting errors in your web site try out the trail and error debugging method.
Though the World Wide Web consortium has specified the standards for using HTML, you can very well invent your own and design your web site accordingly. But this has a disadvantage that the browser may reject the parts that cannot be executed and the appearance and functioning of your web site will be affected.
The basic difference between the two versions of a browser lies in the support they provide for the HTML. But on top of all it would be better if you pay attention to the browser compatibility while designing your web site. This will prevent you from running in to future issues regarding the incompatibility of the browser.
Posted by
Sunflower
at
3/15/2012 02:34:00 PM
0
comments
Labels: Browser incompatibility, Code, Compatible, Detection, Focus areas, Format, Function, HTML, Incompatibility, Standards, Tools, Translate, Versions, Web Applications, Web browser, Web pages, Websites
![]() | Subscribe by Email |
|
Till now so many types of SQL injection attacks have been identified. But, there is one type of SQL injection type which results in to different kinds of combinations of the other SQL injection attacks. This type of SQL injection attacks are commonly known as the compound SQL injection attacks.
This type of SQL injection attack has been derived from rigorous research and experimenting with the different SQL injection attack vectors putting them in different combinations with the various other web application attacks.
Some of the most commonly employed combinations are:
1. SQL injection + XSS cross site scripting
2. SQL injection + DDos attacks
3. SQL injection + insufficient authentication
4. SQL injection + DNS hijacking
Compounded SQL Injection Attack
- SQL is a language developed for interacting with the data base of the applications and web sites.
- The functions are mainly defined to retrieve the data from the data bases or to update the contents of the existing data bases.
- It uses compound conditions basically that make use of AND or OR.
- A compound statement is used to group all the other statements so as to constitute an executable block.
- SQL variables can be declared in an atomic compound statement that has been dynamically developed.
- A compound statement can be easily embedded in to SQL functions, SQL methods, trigger etc.
- To invoke a dynamic compound statement no privileges are required, although the authorization ID of the compound statement needs to include all the privileges required invoking the other SQL statements that form a part of that particular compound statement.
- Most of the compilers compile the compound statements as one single statement since this technique proves effective for the short scripts that do not require little control flow logic though a great data flow.
- For larger scripts or constructs, it’s better to use the SQL procedures.
- The “discretize” function is quite a simple one and is often used for the classification and modification of the data and gives back a NULL value for the malicious data.
- Later this malicious data is cleansed up by the compound statement.
- Most of the mechanisms can be elaborated using the technique of multi stage cleansing.
- The advantage of the compound statement is that here the FOR loop neither does open up a cursor nor the single row inserts are treated so.
- Here the underlying logic is of a multi table insert that has been selected previously.
- This advantage is reaped by compiling the dynamic statement as a single one.
- In contrast to this dynamic compound statement, there’s another type called Compounded SQL embedded statement.
- These statements can only be embedded in to the applications.
- In contrast to the dynamic statements, these cannot be prepared dynamically.
- These statements do not required any special privileges for invocation.
Posted by
Sunflower
at
3/13/2012 11:30:00 PM
0
comments
Labels: Applications, Attacker, Authentication, Compounded SQL injection attack, Data, Database, Dynamic, Functions, Logical, Methods, Modify, SQL, SQL injection attack, Statements, Web Applications, Websites
![]() | Subscribe by Email |
|
XSS or cross site scripting attack is a much familiar security threat in today’s cyber world and is taking a toll on the web sites and applications by breaking in to their security system.
What is Cross Site Scripting Attack?
- Cross site scripting attack is another attack categorized under the category of computer security vulnerabilities which are the most common and frequent among the web applications.
- These attacks are known for making the web application so vulnerable that the malicious outside attackers are able to inject the malicious client side scripts in to the web pages or applications that are later set for the view by the users who visit the page.
- Another nefarious purpose of these attacks is to incur the access controls like the same origin policy.
- The cross site scripting attacks account for almost 80 percent of all the security threats identified and documented in the year of 2007 till now by the Symantec.
- The cross site scripting technique for the good purpose is usually employed for curbing risk depending on the measure of the sensitivity of the data that is being processed by that particular web site or web page.
- Apart from this factor, another factor that makes it easy for the attacks to happen is the security mitigation as implemented by the owner of that web site.
- Cross site scripting attacks are employed by some people to create petty nuisance.
- This is nothing but the misuse of the vulnerability of the security system by the attackers for bypassing the security mechanisms on the client side which are usually implemented by the web browsers up on the web content on the web site.
- There are various ways through which the site can be attacked and accessed for injecting the malicious scripts in to them.
- Such ways or methods can provide the attacker an unauthorized and easy way to access all the sensitive content of the page, information of the user activity as stored by the web browser and session cookies etc.
- Cross site scripting attacks are a type of code injection attack and somewhat similar to the SQL injection attacks.
- Earlier the cross site scripting technique was seen as the loading of the third party application that had been attacked at an unrelated attack site while the execution of the java scripts took place in the context of security of the domain on target as created by the attacker.
- Eventually this cross site scripting attacks were carried out through different modes of the code injection using non java script vectors (like VBscript, flash, Java, ActiveX, HTML, SQL and so on).
- Cross site scripting attacks are a consequence of the cross site scripting vulnerabilities that have been under exploitation since the advent of 20th century.
So many famous social networking sites of today like my space, orkut, twitter, Facebook etc have witnessed these attacks in the past. With the advancement of the cross site scripting techniques, they have now successfully surpassed the vulnerabilities like buffer overflows reporting to be the most common security vulnerability. Even now around 60 percent of the total web sites have been sorted as vulnerable to the cross site scripting attacks.
As such there are no defined criteria for the classification of the XSS flaws, but according to the experts they are classified in to two categories:
1. Persistent XSS flaws
- Also known as stored XSS flaws and is the most destructive type.
- Occurs when the data which has been provided by the attacker is stored by the server.
2. Non persistent XSS flaws
- Also known as reflected XSS flaws and most common type.
- Occurs when data from a web client is used by server scripts for generating required pages without the sanitization of the queries.
Posted by
Sunflower
at
3/13/2012 01:50:00 PM
0
comments
Labels: Application, Attacker, attacks, Client, Client side scripting, Content, Control, Cross site scripting, Information, Injection, Security, Techniques, Test Scripts, Users, Web Applications, Websites
![]() | Subscribe by Email |
|
Content spoofing is a rarely discussed topic and is much unheard by the many of us!
So let's evaluate the concepts of content spoofing in detail:
- Content spoofing has been categorized as an attack technique using which the attacker is able to inject a malicious code or payload in to the good content of a web site or a web application.
- This malicious payload or code is later thought of as being the legitimate content of that particular web site or web application which is a wrong interpretation.
- Content spoofing affects usually the web pages which have been built dynamically.
- Text only content spoofing is the technique in which the payload usually as text is passed in to the body of the web page or application in the form of a query string value.
- This approach usually takes effect on the pages of the web sites displaying some news entries and error pages.
- Such content is then later posted on the web site as its legitimate content.
- So when the users visit that particular link they perceive that the spoofed content is nothing but the legitimate content.
- In some cases it is possible that the pay load may exist on the web page for a longer time than estimated.
- Most of the web pages have been built dynamically with the sources from the HTML (hyper text mark up language).
- The attacker can easily change the content and when the particular web page is accessed by a browser, the location comes of the same domain as the user expected but the user does not come to know that the content is not legitimate instead it is shrouded one.
- As this is not enough to harm a web site, some attackers even manage to send malicious links to the users through emails and messages.
- In some cases the malicious links can be enforced up on the users following a cross site scripting attack.
- When the user clicks that link, he/ she visits the web page designed by the attacker with the malicious URL (uniform resource locator).
- The user will not come to know about this that he/ she is actually viewing am unauthentic web page.
- They will unknowingly believe that the spoofed content that they are viewing is purely authentic but this is not the case.
- Content spoofing does nothing but spoils the trust that the user has on the web site.
- The technique of content spoofing is being used like anything for the creation of fake web sites including fake login pages, press releases and defacement.
- Another point to be noted is that if you can fall victim to a cross site scripting attack, then the chances are that you may fall prey to content spoofing attacks as well.
- Content spoofing is a type of exploitation activity used by the hackers who have wrong intentions like presenting certain web pages to the user as if they are legitimate and not from an external source.
- This is somewhat similar to the SQL injection attacks. In both the cases the victims are defrauded like in phishing.
- Some attackers can even access the data base of a web application stored in a server and alter the contents.
- Content spoofing cannot be readily detected since there is large apparent difference between the actual and the spoofed content.
- The content spoofing carried out with the help of dynamic hyper text mark up language or DHTML is considered to be the most dangerous type since it can be used to form fake login pages.
- When any user inputs his sensitive data (can be a password, credit card number etc) in that page, the data goes directly to the attacker without the knowledge of the user that he has fallen victim to an identity theft.
Posted by
Sunflower
at
3/11/2012 12:51:00 PM
0
comments
Labels: Attackers, Code, Content, Content Spoofing, Database, Detection, Errors, Input, Load, Login, Malicious, pages, Sensitive, Spoofed, Text format, Users, Victim, Web Applications, Web pages, Website
![]() | Subscribe by Email |
|
Negative testing is one of the most sought after software testing methodology. Negative testing is the counterpart of positive testing.
Facts about Negative Testing
- Negative testing is really very helpful when it comes to handling the invalid input test data and abnormal behavior of the software system or application.
- The purpose of the negative testing is to prevent such situations in which the invalid data might be taken by the system and which in turn may disrupt the functioning of the whole software system or application.
- For example, when a user tries to enter numerical data in the alphabetic field, the software system displays a message like “incorrect data type”.
- Such response from the software system or application is required since it avoids the crashing or hanging of the whole system by preventing input of invalid data.
- Not only this, the negative testing helps one improve the quality of the software system or application by knocking out its weak points.
- In positive testing, giving some invalid data as input to the system is considered to be an exception but this is not so in the case of negative testing.
- In negative testing, giving some exceptional input to the software system or application is treated just like a normal event.
- Negative testing is all about testing the exceptions.
- Usually for a better software testing results, both the negative testing as well as positive testing are combined together and implemented.
- Using such a testing methodology provides greater test coverage rather than using just one of the either mentioned software testing methodologies.
Situations which are typically tested by the negative testing:
1. Filling up fields by user
- Most of the web sites as well as web applications require the user to fill up all the fields that are marked compulsory.
- To test this functionality, leave all the marked fields blank and hit the submit button and observe the response of the site or the application.
- The expected outcome here can be a message asking you to fill up all the compulsory fields.
2.Checking correspondence between field and data type
- Negative testing also checks the correspondence between the field and data types.
- For example, the different fields in a form can accept the specified type of data. - To test this, you can enter various sorts of invalid data types in to those fields and check the behavior of the application.
3. Checks allowed limits and data bounds
- It also checks for the allowed limits and allowed data bounds.
- Fields in a form can accept data only within a specified data range and not above or below that.
- This can be tested in two ways. You can either enter value that is less than the lower range of the data or you can enter value that is above the specified range.
- Another example can be of text box which accepts only a finite number of characters.
- You can test it by inputting less or more number of characters.
4. Checking reason ability of input data. - Negative testing is also an effective tool for checking the reasonability of the input data.
- The age fields in some web forms etc do not allow any negative integers and also no floating point value.
- This can be tested by simply putting in the wrong data types like a negative integer.
5. Tests the web sessions
- Negative testing can also be used to test the web sessions either for timing or for log-in purposes.
- There are some web pages for viewing which you first have to log in.
- This can be tested by trying to open that web page without logging in.
Negative testing is pretty easy to be carried out manually, but still you can find many automation tools for it.
Posted by
Sunflower
at
3/08/2012 11:55:00 PM
0
comments
Labels: Coverage, Data, Events, Functional, Invalid, Limits, Messages, Methodology, Negative, Negative Testing, Positive Testing, Purpose, Response, Software testing, Tests, Valid, Web Applications, Websites
![]() | Subscribe by Email |
|