Web Testing – Macronimous Blog

5 must do validation check for every website

Benny — Tue, 29 May 2012 07:18:05 +0000

If you are serious about your website, you can not just settle with what you see, remember your visitors are worldwide, and they use different screens to access your site – they even use their LCD TV(50 inches). Validation of a website is important as it ensures to the norms and standards implied. The following are the must have validations that you should insist your website developer to check. Validation also ensures more diversed visitors with different setups.

1.W3C Markup Validation Service

http://validator.w3.org

2.FEED Validator

http://validator.w3.org/feed/

3.W3C CSS Validation Service

http://jigsaw.w3.org/css-validator

4. Link checker

http://validator.w3.org/checklink

5. Mobile compliance

http://validator.w3.org/mobile/

Believe this, it’s worth spending those extra hours and money. !

The post 5 must do validation check for every website first appeared on Macronimous Blog.

4 site design validations you should do before you deliver

Benny — Fri, 30 Apr 2010 07:20:12 +0000

1. Validate HTML

W3C provides HTML validations, which checks the validity of HTML, XHTML etc.

http://validator.w3.org/

2. Validate your CSS

You should use W3C’s CSS validator tool to validate your style sheets.

http://jigsaw.w3.org/css-validator/

3. Validate site links

Check broken links across the site with W3C’s Link checker tool

http://validator.w3.org/checklink

4. Cross browser compatibility

Check the site on multiple browsers with this tool (You may not have a MAC, but you can you can test the site Mac Safari

https://marker.io/

Even if it’s a simple static site, do them to make the site perfect.

The post 4 site design validations you should do before you deliver first appeared on Macronimous Blog.

Web application testing – 12 simple strategies for developers

Benny — Wed, 25 Nov 2009 10:10:03 +0000

We learn from the projects we do and time teaches us too. The following are 12 simple rules for the developers that we have learned from the customers over a period of time. I hope they will help us to deal better with the customers who teaches us, and improve the deliverables that justify our experience.

1. Test, Test and Test your applications before you send it to QA team

2. Fix all the bugs which you find

3. Remember this: If you forget to include QA in the project schedule and swallow QA time by extending your development time, you are doing injustice to the client, your employer and the worst is to yourself.

3. Fix all the bugs which QA team finds

4. Assure yourself that you leave no faults in your application before sending it to the client

5. Do NOT expect the customer to test your application for yourself. The customer need not be a Testing professional.

6. Make the list of changes and bugs reported by the customer.

7. Schedule them – and Let the customer know the turnaround time to fix them all.

8. Fix them and let the QA check them.

9. Make sure that you make the customer happy, and let him prefer you as their favorite developer.

10. Learn from the bugs; By not repeating them you can become a super developer.

11. If a project has strict deadlines, it needs strict QA.

12. Avoid reporting the known bugs to the client – instead, fix them!

As I said learning never ends, I welcome if your valuable rules or strategies or comments could extend this list. Shoot them as your comments.

The post Web application testing – 12 simple strategies for developers first appeared on Macronimous Blog.

Four Frameworks to perform unit testing in PHP

Benny — Wed, 28 Oct 2009 05:59:31 +0000

Doing Unit testing is helps a team to produce quality application within time by allowing the developer to test the code as soon as they write it. By developing a test document, developers are forced to do rigorous testing before it reaches to QA team. This way the span of life cycle is reduced by avoiding it going back and forth between the developer and the tester. The following few Frameworks help teams to do unit testing efficiently. This way unit testing could become a fun to your developers too.

Four Frameworks to perform unit testing in PHP are

1. SimpleTest

2. PHPUnit

3. phpt

4. SnapTest

SimpleTest:

It’s a Open souce unit test framework created by Marcus Baker for PHP. The test structure in SimpleTest is similar to the Junit and PHPUnit. It contains all of the typical functions in Junit and PHPunit and also includes Mock objects. Simplte Test helps to automate the web application’s regression testing. Regression testing on web applications can be done by parsing the HTML page by using scrpitable HTTP client for simulations like Form submission and clicking on Hyperlinks. Some of the JWebUnit functionalities like web page navigation, cookie testing and form submission are also incorporated in this.

The following link will assist you to get more idea on SimpleTest (http://www.simpletest.org)

PHPUnit:

PHP Unit is a part of xUnit family, which has testing frameworks in it. It provides a framework that helps in creating the test scripts easily and also the functionality to execute the tests and then analyze the results. The tests are arranged into cases in PHPUnit, which is very similar to Simple Test. A case is essentially a class in which public methods are singular independent tests. A test name starts with “test” if the test is a public method. Any test, which is not, a public method will not be taken into account unless interpreted as a test under PHPUnit. Helper methods are very useful for recurring tasks. If used Helper methods to set up a test, the test will be considered as a separate test by the framework. Refrence to assert methods are present inside each and every test. An assertion is mainly taking an expected value and then comparing it with an actual value. If the expected value does not match the actual value, then the test fails. Mock Objects are hugely important component in maintaining a unit test’s segregation from all other classes and resources except the one under test.

The following link will assist you to get more idea on PHPUnit.

http://www.phpunit.de/manual/current/en/phpunit-book.pdf

PHPT:

A phpt test is a small script, which used by the php internal and quality assurance teams for testing PHP’s functionalities. Writing phpt tests helps to make PHP more stable. For writing up a phpt test, we need a basic knowledge on PHP language, a text editor and a method to get the results of the code. Phpt test is used in following scenario: The run-tests.php scripts call the test and it takes different parts of phpt file to name and to create a .php file. The newly created .php file is executed and the output of the same is compared with different sections of a phpt file. The Test pass only when the output of the script “matches” with the output provided in the phpt script. Phpt test will do the following: It tries and breaks the PHP functions. PHPT test check the functions normal parameters as well as edge cases.

The following link will assist you to get more idea on Phpt

http://qa.php.net/write-test.php

SnapTest:

The most powerful unit-testing framework for PHP 5+ is SnapTest. PHP’s runtime language is the only one of its kind that can be used to make the unit test process simpler without sacrificing the agility tests. The philosophy on which the Snap Test was build: Unit testing should be transparent in Snap Test. Complexity of test harness and coding out stub files should be avoided in Snap Test. The obstacle in writing tests should be very less so that it becomes easier to write the tests than writing the code.

Features of the SnapTest are:

• JUnit Compliant Test Harness

• TAP Compliant Test Output

• Runnable from Command Line via .sh or .php scripts

• Full support for mock objects at runtime (minimum parallel structures) as actors and critics

• Extensible add-on system for adapting SnapTest to just about any developer environment

The following link will assist you to get more idea on SnapTest

http://code.google.com/p/snaptest/

Doing Unit testing helps a team to produce quality application within time by allowing the developer to test the code as soon as they write it. By developing a test document, developers are forced to do rigorous testing before it reaches to QA team. This way the span of life cycle is reduced by avoiding it going back and forth between the developer and the tester. The following few Frameworks help teams to do unit testing efficiently. This way unit testing could become a fun to your developers too.

Four Frameworks to perform unit testing in PHP are

1. SimpleTest

2. PHPUnit

3. phpt

4. SnapTest

SimpleTest:

It’s a Open souce unit test framework created by Marcus Baker for PHP. The test structure in SimpleTest is similar to the JUnit and PHPUnit. It contains all of the typical functions in JUnit and PHPUnit and also includes Mock objects. Simple Test helps to automate the web application’s regression testing. Regression testing on web applications can be done by parsing the HTML page by using scrpitable HTTP client for simulations like Form submission and clicking on Hyperlinks. Some of the JWebUnit functionalities like web page navigation, cookie testing and form submission are also incorporated in this.

Download and test your version of Simple test.

PHPUnit:

PHP Unit is a part of xUnit family, which has testing frameworks in it. It provides a framework that helps in creating the test scripts easily and also the functionality to execute the tests and then analyze the results. The tests are arranged into cases in PHPUnit, which is very similar to Simple Test. A case is essentially a class in which public methods are singular independent tests. A test name starts with “test” if the test is a public method. Any test, which is not, a public method will not be taken into account unless interpreted as a test under PHPUnit. Helper methods are very useful for recurring tasks. If used Helper methods to set up a test, the test will be considered as a separate test by the framework. Reference to assert methods is present inside each and every test. An assertion is mainly taking an expected value and then comparing it with an actual value. If the expected value does not match the actual value, then the test fails. Mock Objects are a hugely important component in maintaining a unit test’s segregation from all other classes and resources except the one under test.

The following link will assist you to get more idea on PHPUnit.

PHPT:

A phpt test is a small script, which is used by the php internal and quality assurance teams for testing PHP’s functionalities. Writing phpt tests helps to make PHP more stable. For writing up a phpt test, we need a basic knowledge on PHP language, a text editor and a method to get the results of the code. Phpt test is used in following scenario: The run-tests.php scripts call the test and it takes different parts of phpt file to name and to create a .php file. The newly created .php file is executed and the output of the same is compared with different sections of a phpt file. The Test pass only when the output of the script “matches” with the output provided in the phpt script. Phpt test will do the following: It tries and breaks the PHP functions. PHPT test check the functions normal parameters as well as edge cases.

Load and Stress testing – Tools reviewed!

Benny — Tue, 10 Mar 2009 13:53:56 +0000

Most of the performance issues occur because of high stress in the server. You should perform load testing to know how many concurrent visitors your site can serve perfectly. It is difficult to arrange without the help of a set of actual user. It is the proper way of using advanced automatic load and stress testing tools.

Load Runner

Load runner is the contribution of Hewlett-Packard to the software testing industry for analyzing the conduct and concert of the system by giving an actual load to the system. Load runner can make the application feel the load of hundreds or thousands of real-time users and meanwhile can repossess information from web server’s database servers etc.
When working with Load Runner we work with three different tools Virtual User Generator (VuGen) and Controller and Analysis, which are an inevitable part of the tool.

The VuGen helps a user to record and replay the required actions against the applications under test. The required actions will be recorded in the form of scripts. The user can make modifications in the scripts. When the script is ready, the same is executed by the controller and finally, analysis will give the scenario results in the form of graphs for the user to view and analyze.

QEngine

Note: Q Engine is no longer in sale. We will update this section soon with a better tool that we use.

Advent Net Q engine is a tool that supports both load testing and functional testing for web-based applications. The tool mainly helps to spot the bottlenecks in the application code and eradicate the same then and there. This tool helps your ‘N’ Tier endeavor applications meet heavy user loads during peak hours and have high uptime in production. This testing will provide supply user scenarios and reasonable load types for the application during the load test. The tool can create real-time user actions and perform load tests load with hundreds or even thousands of simultaneous users under active load conditions. The load testing features are:

”¢ Load Test Recording
”¢ Flexible User Scenarios and Dynamic Data Generation
”¢ Real-world Load Simulation
”¢ Distributed Load Testing
”¢ Load Test Reports

SilkPerformer

Borland silk performer is an enterprise-class tool for delivering automated software load, stress and performance testing in an open and shareable model. We can create prevailing, realistic load tests for thousands of users running production scenarios across a broad range of endeavor application environments to identify bottlenecks, and then apply powerful diagnostics to resolve performance issues with help of Silk Performer. Adaptable visual scenario modeling enables any load scenario to be tested and compared … whether it involves a single, massive flood of requests to a website or the expected behavior of an enterprise application under daily heavy load. Any bottlenecks are identified, then spontaneous diagnostic and analysis capabilities help resolve the issue quickly, reducing test-and-fix cycles, accelerating time-to-market, and supporting critical release decisions related to application performance. Test creation, root-cause analysis wizards and Java & .NET deep diagnostics build it amazingly simple and efficient to use, removing the cost and complexity associated.

Few Performance & Load Testing Capabilities in Silk Performer:
”¢ Virtual user “types” enable shared, reusable access to load testing across all major application environments
”¢ No license requirement for “controllers” or individual “protocols” means greater access to test creation and execution for more team members across the organization
”¢ Discover ease of use with the built-in step-by-step workflow wizards
”¢ Create tests and executions with Silk Performer’s intuitive interface or leverage the Eclipse IDE
”¢ Test a wide range of enterprise environments with versatile, sharable, multi-protocol virtual-user types
”¢ Easily customize tests with random user data””without programming a single line of code
”¢ Reuse test cases in different environments and scenarios without changing test scripts

WAPT(Web Application testing)

WAPT is a load and stress testing tool for websites, web servers, and intranet applications with web interfaces. WAPT provides easy-to-use ways for accurate load simulation and Run-time test data generation. We can test and analyze the performance characteristics in various load circumstances to find bottleneck of your web applications. WAPT can simulate multiple users for each scenario, custom implement delays between requests and dynamically generate test data parameters. The values of request parameters and URIs can be calculated in a number of ways and even be determined by the server response to the previous request. The features of WAPT are to test websites with dynamic content and protected HTTPS pages. It provides useful test results through descriptive graphs and reports. Additional features included in WAPT: support for secure sites and user authorization, simultaneous testing and batch operation.

The post Load and Stress testing – Tools reviewed! first appeared on Macronimous Blog.