Showing posts with label Documents. Show all posts
Showing posts with label Documents. Show all posts

Wednesday, April 25, 2012

Cross browser compatibility testing tool


Adobe Browser Lab:
Adobe BrowserLab is without a doubt my favorite free cross browser compatibility testing tool on the web.
Adobe BrowserLab allows you to select what browsers and operating systems you would like to test on – everything from IE6 on a Mac to Firefox 5 on Windows.  It lets you save “sets” of browsers, compare browsers via dual or quad comparison windows and even allows you to control the zoom of the browser window. You can change which browsers you’d like to test under “Browser Sets.”
With a sleek interface, an almost instantaneous refresh rate and a comprehensive browser test list I’d wager that Adobe’s BrowserLab will meet a majority of people’s browser testing needs. Most likely only those operating corporate or e-commerce websites need the additional functionality of a tool like Litmus.
The best part about Adobe’s BrowserLab? It’s 100% free! Just sign up for a free Adobe account and start testing!
https://browserlab.adobe.com (free!)

Don’t forget it’s important to not only test browsers but different browsers on different OS’s (which the tools above do). Here’s a handy cross browser testing checklist you can refer to while cross-browser testing your website or application:

1)      Validate your CSS, HTML and XHTML
2)      Test your Ajax, JQuery and Javascript functionality
3)      Confirm accurate font size and font display
4)      Confirm accurate page layout, alignment and resolutions
5)      Test and confirm page displays properly when zoomed in/out in browser.
6)      Check for broken applications and links.
7)      Confirm all scripts and forms work.

Monday, April 23, 2012

Website Checklist


IN RESPECT OF WEBSITE

1. User Interface Testing
A. Easy to use
B. Instructions are simple and clear. Additionally, test that instructions are
correct
C. Is the site map is correct?
D. Does each link on the map actually exist?
E. Are there links on the site that are not represented on the map?
D. Is the navigational bar present on every screen?
E. Is it consistent?
F. Does each link work on each page?
G. Correctness of wording
H. No overuse of bold text,big fonts and blinking
I. Hyperlinked references are working
J. Are patterns, background colour and pictures distract the user?
K. Does all images add value to respective page?
L. Do these images waste bandwidth? In general use small pictures to reduce load.
M. Does wrap-around occurs properly?
2. Functionality Testing
A. Correctness of the functionality of the website i.e. the part that interfaces with the server and actually “does stuff”.
B. No internal and external broken links.
C. User submitted information through forms, needs to work properly.In order to test this, verify that the server stores the information properly and that systems down the line can interpret and use that information.
D. User input should get verified at system level according to business rules and error/warning messages should be flash to user for incorrect inputs.
E. If the system uses cookies, make sure the cookies work. If cookies store login information, make sure the information is encrypted in the cookie file. If the cookie is used for statistics, make sure those cookies are encrypted too, Otherwise people can edit their cookies and skew information
3. Interface Testing
A. If site calls external servers for additional data, verify that the software can handle every possible message returned by the external server.
B. To test browser and server interface, run queries on the database to make sure the transaction data is being retrieve and store properly.
C. Make sure system can handle application errors.
D. Make sure that system can handle other systems’ errors. e.g. losing the internet connection from server to the external server.
E. How the transaction is handled, if user does not initiate interruption.
4. Compatibility Testing
A. Operating systems
B. Browsers
C. Video settings
D. Printers
5. Load/Stress Testing
A. How many users at the same time can access without getting busy signal?
B. Can system handle large amount of data from multiple users?
C. Long period of continuous use: is site able to run for long period, without downtime.
6. Security
A. Each directory should have an index.html or main.html page so a directory listing doesn’t appear.
B. Historical pages should be removed from directories.
C. In order to validate users, if site requires user to login; verify that the system does not allow invalid usernames/password.
D. Is there a maximum number of failed logins allowed before the server locks out the current user?
E. Verify rules for password selection.
F. Does the server log track every transaction?
G. Does it track unsuccessful login attempts?
H. What does it store for each transaction?

Testing checklist


The list is equal to the Test Plan, it will cover all quality assurance and testing standards.

Testing checklist:
Creation of System and Acceptance Tests
Start Acceptance test Creation
Identify test team
Create Workplan
Approach Create a test
Acceptance Criteria and Requirements Link to form the basis of admission test
Use subset of the system test cases to form the requirements of section admission test
Create Scripts for use by consumers, to show that the system meets requirements
Create a test plan. Include all people and other resources
Conduct Acceptance Test
Start Test Creation System
Identification of test team members
Create Workplan
Determine resource requirements
Identification of productivity tools for testing
Determine data requirements
Reach agreement with the data center
Create Test Approach
Identification of any structures that are needed
Take and review existing exhibit
Create inventory of test items
Identifying Design states, conditions, processes and procedures
Determine the need for code-based (white box) testing. Identification of conditions
Identify all functional requirements
End inventory creation
Start creating test case
Create test cases based on the inventory of test items
Identify logical groups of business functions for new system Divide into test cases to test the functional groups traced item inventory
Design sets of data correspond to the test cases
End test case creation
Review of business functions, test cases and data sets to users
Get signoff on test design from project leader and QA
End Test Design
Start Test Preparation
Get support resources test
Outline the expected results for each test case
Take the test data. Validate and trace to test cases
Prepare detailed test Scripts for any test case
Prepare & File established environmental procedures. Include and support recovery plans
End Test Preparation phase
Perform System Test
Scripts execute test
Compare the actual result is
Document discrepancies and create a problem report
Preparation of maintenance phase input
Re-execute test group after repair problem
Create test final report, include the known bugs list
Get formal sign-off


How to increase internet speed


I want to share with you an important thing about increasing  internet speed.  Here is a solution for all Internet Lovers…..
1) Click on Start Menu –>  Run .
2) Type in Run  :- gpedit.msc
3) Local Computer Policy>Computer Configuration>Administrative Templates>Network>QoS Packet Scheduler>Limit Reservable Bandwidth>. If  it’s  disabled then click on enable.
4) You can see there 20%. Change it to 0%
5) Apply then ok
and restart your system and check your internet speed.
This 20% is your internet bandwidth which is eating by the windows without showing any thing.
Check and Let me know
Cheers….

How to evaluate Website Quality


 Below is the catalog, composed with a view to quickly obtain data for basic website quality rating.

1. Evaluate Standards
The webpage which fails to comply with the standards could have different errors, which are very difficult to predict. Starting from the problems in different browsers, to poor Google indexing. With the help comes the W3C, which sets standards and provides ready to use tools:
* HTML, XHTML – http://validator.w3.org/
* CSS – http://jigsaw.w3.org/css-validator/
* FEED (RSS or ATOM) – http://validator.w3.org/feed/
2. Evaluate Design
The design has many meanings, here it comes mainly about how the site will be looked in different environments. Is not too wide, too high and looks the same in Firefox or Opera.
* Plenty of browsers, systems, etc – http://browsershots.org/
* Look at webpage in different resolution – http://www.markhorrell.com/tools/browser.html
3. Evaluate Performance
Underestimated but very important issue: the speed of page loading. We can have beautiful graphics, animations and great scripts but the user may not wait for full page load. Remember that we need to count the full load, not just the size of the HTML source, but also images, flash, ads, scripts and dynamic content via AJAX.
* Popular, cute tool – http://tools.pingdom.com/fpt/
* Overall page performance – http://site-perf.com/
4. Evaluate SEO Quality
Search engine optimization is a difficult and lengthy process but most mistakes are the same, easy and crucial errors that substantially reduce the Google ranking. The following tools, which very quickly learn us problems at the site in terms of SEO:
* Complete SEO Analyzer – http://www.seoworkers.com/tools/analyzer.html
* Google Webmaster Guidelines – http://www.google.com/support/webmasters/bin/answer.py?answer=35769
5. Evaluate Linking
Dead links are strictly connected with bad SEO score. Good to have many inner and outer links, but not too many and all must live Google Webmaster Tools are very useful particularly for the analysis of the number of links from other sites.
* W3C Tool – http://validator.w3.org/checklink
* DeadLinks – http://www.dead-links.com/
* Google Webmaster Tools – https://www.google.com/webmasters/tools/
6. Evaluate Accessibility
Accessibility lies close to the Usability which is hard to check by machine. We have standards for websites accessibility and tools to rate it.
* Great, visual tool – http://wave.webaim.org/
* Compliance with standards – http://www.contentquality.com/
* Standard – http://www.w3.org/TR/WCAG10/
* Standard – http://www.access-board.gov/508.htm

Conclusion
The above list is not comprehensive and thorough but gives a elevated prospective to rapidly confirm whether provided website has the basic and crucial defects and the website quality is improved noticeably