WEB TESTING

WEB TESTING:


While testing a web application you need to consider following Cases:

• Functionality Testing
• Performance Testing
• Usability Testing
• Server Side Interface
• Client Side Compatibility
• Security

Ø      Functionality:
In testing the functionality of the web sites the following should be tested:
• Links
i. Internal Links
ii. External Links
iii. Mail Links
iv. Broken Links

Ø       Forms
i. Field validation
ii. Error message for wrong input
iii. Optional and Mandatory fields

Ø      Database
* Testing will be done on the database integrity.

Ø      Cookies
* Testing will be done on the client system side, on the temporary Internet files.

Ø      Performance:
Performance testing can be applied to understand the web site’s scalability, or to benchmark the performance in the environment of third party products such as servers and middleware for potential purchase.

Ø      Connection Speed:
Tested over various networks like Dial Up, ISDN etc
• Load:
i. What is the no. of users per time?
ii. Check for peak loads and how system behaves
iii. Large amount of data accessed by user
• Stress:
i. Continuous Load
ii. Performance of memory, CPU, file handling etc..

Ø      Usability:
Usability testing is the process by which the human-computer interaction characteristics of a system are measured, and weaknesses are identified for correction.
• Ease of learning
• Navigation
• Subjective user satisfaction
• General appearance

Ø      Server Side Interface:
In web testing the server side interface should be tested. This is done by verify that communication is done properly. Compatibility of server with software, hardware, network and database should be tested.

Ø      Client Side Compatibility:
The client side compatibility is also tested in various platforms, using various browsers etc.

Ø      Security:
The primary reason for testing the security of a web is to identify potential vulnerabilities and subsequently repair them.
• Network Scanning
• Vulnerability Scanning
• Password Cracking
• Log Review
• Integrity Checkers
• Virus Detection

The Top 25 Mapped to Application Security Methods

The possible ways such as Education,Manual Process,Using Tools and Threat Model of finding the vulnerability using the web application security testing process as mentioned below picture.

Use Enumerations for web application security testing.

Enumerations help identify specific software-related items that can be counted, aggregated, evaluated over time

CVE->Common Vulnerabilities and Exposures.
CWE->Common Weakness Enumeration.
CAPEC->Common Attack Pattern Enumeration and Classification.

The Class were  mentioned CVE,CWE,CAPEC below.

SQL Injection XSS Attack Buffer Overflow Directory Traversal PHP Include Symbolic Link Authorization Bypass Dos Malformed Input Information Leak

Integer Overflow CSRF Bad Permissions Hard coded Password Weak Crypto Insufficient Randomness Search Path Sensitive data root Dos Flood Eval Injection

Automated Software Testing for the User Interface

Eggplant is automated QA test software that is...

 non-invasive

 technology agnostic

 easy to script and use

EggPlant is image-based – which means it can “see” the user interface, just as the human eye does. The difference is, EggPlant can test your software using a fraction of the time and resources.

We can test any operating system – Mac, Linux, Windows , Solaris, Symbian, Blackberry, Windows Mobile, KVM Switches

We can test any interface – screens, POS, command and control systems, air traffic control screens, smartphones, mobile devices.

Software may have perfectly written code and still result in inaccuracies at the user interface. Do you want to find the flaws or wait until your customers point them out?

If you need functional, regression, integration, load, user experience, GUI,Multi-media, Mobile, QoS, or SLA testing – we can assist you!

Security testing.

Security is a very critical aspect of Web Applications, keeping in mind the alarming rise in cyber crimes and intrusion attempts by malicious users. The financial losses and legal consequences that organizations can face due to security incidents are immense.

This paper addresses some of the common maladies faced by QA Personnel and Customers from a SecurityPerspective. It describes the common Security vulnerabilities in applications with examples and techniques for testing the application for those vulnerabilities. Modelling techniques are discussed that help in identifying vulnerabilities and evaluate the Security Risks for an application. The paper suggests Processes, Framework, and Tools to help in providing highly effective and low cost Security Testing Solutions (specifically Penetration
Testing) for Web Applications. Embedded in the paper are Traceability Templates, a Test Plan Template, a Checklist and a Process flow for Security Testing.