Manual Testing
Our team conducts various types of manual testing by executing test cases. This process ensures that we thoroughly validate software features and identify any potential issues.User Interface
In UI testing, our goal is to ensure that the website matches the intended design precisely. When we say “pixel perfect,” we mean that every element should have the same appearance down to the smallest detail as specified in the design, while also maintaining consistency throughout the interface. Some testing tools we use to verify UI /UX :- Browserstack: For cross-browser and responsive testing
- CSS Viewer: Chrome extension to check css stylings
- Measure Everything: Chrome extension to measure spacing and element distance.
- WhatFonts: Chrome extension to check the fonts stylings
Functional
In functional testing, our aim is to ensure that the website behaves as intended. We’ve developed standardized test case templates, which are available on our Confluence platform. These templates are used based on the specific project and requirements, helping us maintain consistency and efficiency in our testing processes.Cross Browser & Responsive Compatibility
We conduct Cross Browser and Responsive Compatibility Testing to ensure our projects work seamlessly across different browsers and devices, providing a consistent user experience.Web Analytics
We use the Google Analytics Debugger Chrome extension to verify JavaScript console information and validate Google Analytics tracking code implementations in real-time. This ensures accuracy and reliability in our web analytics data.- Google Analytics Debugger: Chrome extension to verify Javascript console information and validate Google Analytics tracking code implementations in real-time
WP debug logs
WordPress comes with specific debug systems designed to simplify the process as well as standardize code across the core, plugins, and themes. We check debug logs to increase the overall quality and interoperability of the code. Let’s check how we use these constants in detail. WP_DEBUG To enable debugging mode, add the following line to thewp-config.php file
define('WP_DEBUG', true);
WP_DEBUG_LOG
When WP_DEBUG_LOG and WP_DEBUG are enabled, WordPress saves all error information to the debug.log file in the wp-content directory. By default, this setting is disabled.
To enable this setting, add the following line to the wp-config.php file
define( 'WP_DEBUG_LOG', true);
WP_DEBUG_DISPLAY
When WP_DEBUG_DISPLAY and WP_DEBUG are enabled, WordPress displays an error and warning messages on web pages. By default, this setting is enabled. When this setting is disabled, debugging messages are hidden from view.
To disable this setting, add the following line to the wp-config.php file
define('WP_DEBUG_DISPLAY', false);
How to open wp-config.php file
For updating the wp-config file, open the terminal and login to your server where the site is hosted (or jump to the local setup.) This file is located inside the root directory of the project folder.
- Open the terminal
- Go to the folder where your WordPress set up is created
- Open
wp-config.phpfile with editor. for example: visual studio - Add the line of codes as mentioned above
- Save the changes and quit from the editor.
Don’t forget that
WP_DEBUG is for local development use only and should not be used on live sites.Accessibility
Everyone must contribute to web accessibility, from developers, editors, designers, theme builders, and content creators. This early stage testing and adjustment prevents surprises and extra work later on, streamlining the project. These tools are useful for testing accessibility:- WAVE Web Accessibility Evaluation: Web Accessibility Evaluation Tool
- axe DevTools : Provides detailed accessibility reports directly within the browser
- HTML_CodeSniffer: Check your HTML code conforms coding standard
- Color Contrast Analyzer: Investigate color contrast ratios.
- WebaXe: Broad overview of tools
- ColorA11y: Chrome Colour contrast browser extension for Google
- Sim Daltonism: Colour blindness simulator
- JAWS, VoiceOver (Mac), Narrator (Windows), NVDA (Windows): Screen Reader