Forem: deekshalt

Why Software Testing Is Necessary?

deekshalt — Wed, 28 Sep 2022 09:00:47 +0000

Test your mobile website or mobile app for free and get started right away. You can use on-cloud based Android emulator online to see how your website/app will appear on a real, emulated device. All you need is a browser; no software install or signup required!

Software Testing has been the buzzword in the software industry for a long time. Even after years, its charm still remains the same. So what’s the main reason behind it? Why is it necessary? Let’s explore this in this Infographic.

Test your web and mobile apps on Android Emulators online to ensure that they are compatible with latest and legacy Android operating systems, devices, and browsers.

If you want to know about regression test, check this out: what is Regression testing, its importance and types, and how to perform it.

Browser Statistics To Decide On Your Cross Browser Testing Needs

deekshalt — Wed, 28 Sep 2022 08:00:40 +0000

The question that has been revolving around people’s minds is ‘How to formulate a Cross Browser Testing Strategy’? The answer usually revolves around what are the most popular browsers of your target audience. You start by covering the most popular browsers in your test coverage followed by the least used. This infographic on browser statistics is going to help you decide which browsers to target first for your cross platform test coverage.

LambdaTest is an online test execution cloud that allows you to execute your Selenium, Cypress, Appium, and JavaScript test automations builds online . You can run your scripts, in parallel, across 3000+ different browsers and devices. All real machines, running real OS and real browsers. Therefore with LambdaTest, you not only cut down your test execution times by running tests in parallel, you also increase your browser coverage, and thus ensure your users get best experience no matter what device they use.

Check this out- Automation Testing Platform: Accelerate your release velocity with blazing fast test automation on cloud

Check this out- Online Automated testing Platform

What Is Usability Testing And Why You Need It?

deekshalt — Mon, 26 Sep 2022 14:21:45 +0000

Usability testing, as the name goes, is the testing of a website or an application for its usability. By usability one might confuse it for an ‘ease of use’ of any website or product , but it’s not limited to just that. Usability is a wide term and there is a lot more to it but don’t worry at the end of this blog, you’ll be clear with every point of usability and mobile usability testing.

Before going into details of usability testing, you need to be aware of what usability is and why does it matter. As per ISO, one might think of usability as:

The extent to which you can use a product to achieve goals effectively, efficiently, and with proper satisfaction in a certain context of use of a product.

These lines define the core underlying spirit behind usability testing. No matter the product or product use case, even if the parameters defining the usability of a product will change, the key characteristic and the underlying principle behind usability testing remains the same.

If explained in brief, usability testing:

is highly concerned with user satisfaction, irrespective of the product requirements, engineering used, and other factors considered while building the specific product. It is like performing a black box testing of a product just to gather the ease of use, effectiveness, efficiency, and satisfaction related to the product’s usage.
is related to how usable the product or website is. If some website has to be usable, it has to be engaging and pleasing, and at the same time perform the intended task in as intuitive and efficient way possible.

If you are new to E2E Testing, you must look out this guide! A Complete End to End (E2E) Testing Tutorial: Comprehensive Guide With Examples and Best Practices

Why We Need To Be Concerned About Usability?

As per the latest stats:

46% of the people leave a website after getting an unclear picture of what your website does.
44% of people leave a website as they find insufficient contact information in the website.
37% people decide to never come back to a website because of poor design or bad navigation.

And the ratio of these bounce backs is quite high. Any business cannot afford to lose this portion of the audience hence it becomes necessary to perform usability testing and making sure that you won’t miss out on such high number of your website visitors.

In other words, If a user visits your website and it fails to meet their goals in an intuitive, efficient, and satisfactory manner what will they do?

Go for its competitors!

User experience is one of the most important if not the most important aspect of making an online business successful. And that’s what is measured under the scope of Usability Testing.

Check this out- Selenium Tutorial: A complete guide on Selenium automation testing

So, What All Is To Be Tested For Testing Usability Of A Product?

In simple terms, when you are testing for usability, you need to test for 5Es namely:

Effectiveness
Efficiency
Engagement
Error Tolerance
Ease of Learning

So, let’s get into details of these 5Es. What they mean and what all you’ll be testing for them?

Also check out Top Usability Testing Tools For Your Website

1. Effectiveness

Effectiveness means whether the user will be able to achieve the goal accurately or not.

When performing usability testing, you need to make sure that your website/ product actually solves the core user problem or not.. The scope of this testing ranges from features, functionality, to even content. In features part is easy to understand. The product should have the critical features to solve the problem that has been advertised by promoters Here promoters can be a website, social media, person, etc. In other words face of the product that is being marketed to bring users on board.

The same goes for content. You need to use a clear and simple language in order to make sure that your message is clear to the user and the language is pretty easy to understand.

Now that you have a feature set, you need to make sure that these features works as intended. And that’s what is covered under functionality testing.

2. Efficiency

Efficiency is highly concerned with the speed of achieving a certain goal. The faster you achieve a goal, the more efficient you are.

For any website, you can measure efficiency in terms of number of keystrokes required to achieve a certain goal. Less number of keystrokes with clarity and achievable goal is considered highly efficient.

Navigation is one of the factors determining the efficiency. How intuitive the website’s navigation is? Do users feel confused or find it tiring while navigating from one page to another? How many pages the user has to go through while completing a certain goal?

For example: If you went to an ecommerce website to purchase a pair of sunglasses. What will be your workflow?

Login to the Web Portal
Search Sunglasses in the search box
Click on Search results to find the relevant sunglasses for you
Go to cart
Move to checkout
Redirected to payments page
Add pin, OTP, or other authentications
An invoice will be finally generated along with product delivery and tracking details

So, if you analyze it you’ll find out that it involves 8 page navigation to attain that particular goal plus it sends you in another workflow of shipping and tracking for finally receiving the product. In this case, it’s an ideal scenario however, if some unnecessary navigation pages are there, there is a need to decrease that and make it as minimum as possible. Shortcuts also adds to the efficiency of a product or website. So check for all the shortcuts and all possible ways to speed up the user’s goal attaining pace. This enhances the user experience and saves his time and efforts making it more usable.

Latest advanced websites deliver web pages to users based on their past usage pattern to get a better conversion. For example, suppose the user has not selected a sunglasses in the above scenario, the website will now show sunglasses as default products in homepage on user’s next visit. Maybe highlighting any ongoing offer or any new addition to the product list.

3. Engagement

By engagement we mean the capacity of tending the user to stay on our product or website as maximum as possible. It is a quantitative field to be tested.

This can be affected by minute elements like design elements, good visuals, better graphics, micro-interactions, chat-bots, surveys,etc. Aesthetics plays a major role in keeping a user engaged. The way you present your product or website also gives you an edge over engagement.

So, you need to test this by keeping a check on time, what all things are there on a website or a product that are increasing the interaction time on a website. Make sure that interaction time is increased because of user’s interest and not because of the problems holding him back to take any action. You need to keep an eye on bounce rate, average session time, and total number of sessions. For products you also need to keep track of engagement cohorts.

Engagement is about looking nice and right at the same time. So you need to test for all the nice and right elements.

4. Error Tolerance

It relates with how can you minimize errors from occuring in your website or product. Some small small inclusions like undo, redo, etc can help you making your website error tolerant.

Make sure whenever, something can happen by mistake, do you have any ‘get back to original’ option for that? It will add to the usability of your product. So, to test for it, try every possible mistakes that you can do and is there a way to recover them?

5. Ease of Learning

That is also one of the most important things to be tested for usability. Ease of learning means how easily are your users learning to use your new product and feature updates.

For example, your users were loving your product’s current version and an update changed the way it works. Now there might be a possibility that the new version is disliked by them as they are unable to understand how they have to use it now.

So, before making any release to the market or making it available for the users, perform a through testing from an end user’s perspective.

The major problem that occurs while doing so is that we can’t make out what all possibilities can there be available for our user. He might be a beginner, intermediate, and an expert so while performing usability testing, we have to take care of all the possible scenarios and make our product up to their expectations.

Hey! Do you know, you can run your Playwright test scripts instantly on 50+ browser and OS combinations using the LambdaTest cloud.

What Are The Major Advantages Of Performing Usability Testing?

When you perform usability testing, you’ll

check if the product meets the user expectations or not
make sure that the business decisions are matching the real world use
find out flaws in the product before the users find them
get a clear picture of how successful your users are when performing tasks
get feedbacks for your product and improve your product for better usability.

Once you’re clear on what is usability and what and why we need to perform usability testing, you now need to create a time saving and effective usability testing strategy. Well that’s too much to digest in a single time so I’ll help you with this problem in the next blog. Till then Ciao and Happy testing!

Why Automation Testing Is Important In Agile Development?

deekshalt — Wed, 01 Jun 2022 11:21:50 +0000

There have been continuous advancements in Software development technologies. When talking about software development methods one can simply not ignore the role which testing plays in software development. Therefore in order to maintain pace with latest software development technologies testing needs to be done faster than development.

Imagine you are building a big Software-as-a-Service product like for example Salesforce. The product has a 1000 features. You also have to release a new feature every other month so as to keep up with competition. Now imagine that you have to test that product. Check if new features have not affected old features and every features is working fine. All 1000 of them. Now imagine that you have to test the whole software within a week.
No possible right. That’s what enterprise developer thought and therefore automated the process of testing.

What the scenario was ‘before-Agile’?

Before the advent of Agile software Development, Waterfall Development Technology was the prevalent software development model. Waterfall model involves development in a series of steps starting with planning, designing, development, and testing. However the most salient feature of this model was that next phase is executed only when the previous phase is completed. That means that the testing of the product is done at the very last stage. If certain new requirements are added by the user at an advanced stage then the only option left is to re-develop the application with the new user demands. Or say the testers detect a bug, then the whole process has to iterate to locate the phase in which the bug was introduced. Moreover, the product could only be deployed once it is completely built so it takes a lot of time for the market release.

How Agile Development works?

In Agile, testing and development is done in several iterations. Agile Development method incorporates the concepts of Continuous Integration, Continuous Development, and Continuous Deployment. Continuous deployment can only be possible if the product is continuously tested as well. Faster testing calls for faster and advanced testing methods. If in a SDLC, the development is going on at a faster pace and testing is not able to cope up with that speed then you can imagine Agile falling out of its way. You will not be able to implement Agile with slow testing methods.

Check this out: CSS font-stretch - The font-stretch property allows the browser to select the appropriate font variation based on a specific width.

So Where Does Automation Testing Fit In Agile Development?

To fulfil the needs for fast deployment, testing methods need to be faster. To understand this, let’s take an example of an application developed. Consider that a gaming application is being developed. In the first build, the game is deployed into the market. Now with every update new features are added to the application. So the gaming application will be continuously deployed with every new feature being tested along with the existing features. With so many features it becomes almost impossible to test every feature manually. This is where automation testing comes into picture.

Automation testing can solve your problem for fast testing methods if proper tools are used in an effective manner. There are various tools that are available for automation testing process such as: Selenium, TestNG, Appium, Cucumber, Test Studio, etc. These tools require a test case to be developed according to the needs of application/software to be tested. These test cases can then be run multiple times while performing continuous builds. This ensures that every step being taken is bug free or if a bug is introduced then it becomes easy to identify at what stage it has entered into our program.

When should you apply Automation Testing in Agile Development?

If a single test case is to be tested repeatedly.
If your test cases are very tedious and time-consuming.
If you have to run the test cases with different data and conditions several times
If you a similar test suite that needs to be executed for different user sets.
If you have got a narrow release window, and saving time is your top priority.
When test cases need to be executed with various browsers and environments

This certification is ideal for testing professionals who want to acquire advanced, hands-on knowledge in Selenium automation testing.

Here’s a short glimpse of the Selenium Advanced certification from LambdaTest:

Hey! Do you know the CSS :focus-within pseudo-class identifies elements that either match the :focus pseudo-class or have descendant elements that do.

Things That Make Agile Developer’s Life Difficult

An agile tester may face various challenges. Some of them are listed below which can be overcome by using proper testing methods

Detection of defects at an early stage:

It becomes easier and cheaper to fix a defect if it is detected at an early stage but in case the defect is found at the later stages of development cycle it becomes more expensive and difficult to fix it. So there are two solutions to this problem: you can do subsequent code reviews or run static analysis tools on source code. These ancillary tools to Automation Testing are aimed at finding missing routines, enforce coding standards , coding standard deviations and errors that can crop up in production due to mismatch data types.

Inadequate API testing:

API testing requires an advanced knowledge of coding because of the complexities associated with the test code. So this is because many a times it may be possible that your API is not tested properly. To ensure this, there are many testing tools available to check the functionality of APIs without the need of strong coding skills so that your services are fully tested.

Inadequate test coverage:

Sometimes you miss out the critical tests for any requirements because of continuous integration and the changing requirements associated with the service. Another cause to miss out the test coverage can be the unanticipated changes being made into the code. So as to make sure that all the changed codes were tested, source code analysis needs to be done to identify the modules that were changed.

Broken code due to frequent builds:

As the code is changed and compiled daily, the existing features being affected by the code becomes more frequent. For this every time the code is changed it needs to be compiled and tested. Because of resources constraint it becomes difficult to perform this daily so the testers need to implement automation testing to do so.

Performance bottlenecks:

With addition of more and more features, the complexity of code also increases. Performance issues will be faced if the developer loses track of how this is affecting the end user performance. So you need to identify which parts of the code are creating problems and how the performance is being affected with time due to these problems. Load and Automation Testing Tools can be utilized to check identify the slow areas and keep track of performance with time.

Do you know, CSS Gradients - A CSS3-compatible method of defining a linear or radial color gradient as an image, to be used in other parts of a style sheet.

Why Agile Developers Love Automation Testing

Faster Speed: Automating the testing introduces speed to our development methodology.
Greater ROI(Return on Investment): Though initial investment cost is high, but due to the advantages the return on investment is one long term and is time saving too.
Reliable Deployments: By employing the use of scripts for the testing procedure reliability is increased to many folds.
Parallel Testing: Same script can run on different devices hence simultaneous testing
Reusable Code Scripts: Once a script a developed, you can use it number of times to test the software bug. Different updations can also be made in the same script to use it for latest user requirements.

In Short

Automation testing is like a backbone to Agile Software Development methodology for the advantages it offers. By applying automation testing to Agile you can easily overcome the challenges faced by Agile.

Automating Testing: A Backbone To DevOps

deekshalt — Tue, 31 May 2022 12:27:22 +0000

There are two wheels in any software development organization: Development and Operations. They both go hand in hand and for the smooth running of both processes, it’s necessary that they run in complete sync and co-ordination. Now to ensure that there is no lingering between operation and software development processes like design, build, test, and deployment, all these teams have to be on the same page in terms of speed and integration. So all these development processes must attune.

Software testing, if not done efficiently, can be the biggest hindrance in the smooth running of any organization. For large and fast development operations and to make sure that the testing team does not lag behind it becomes imperative to implement Automation Testing.

Do you know CSS3 Box-shadow is a CSS3 property that is able to display an inner or outer shadow effect to elements.

So why automation testing?

Automation testing, as the name suggests, means to automate a process and involves less of human intervention. So, why we use automation testing? The main reasons are-

Time-saving: Since it employs the use of test case to detect bugs in the software program, it is less time consuming as compared to other testing methods. If the testing is made faster, then the deployment frequency of the product in the market can increase to an enormous level.
Less prone to errors: As this involves the use of software program to test the application so the chances of human errors are minimized. Manual effort is required to generate the test case and to command it to execute the testing process. So various sorts of human errors are eliminated to a great extent.
Repeated execution: When you need to execute the test case for an ample number of times so as to check the validity of the application then Automation testing can prove to be a boon. Since it consumes less time so repeated execution becomes easy.
Reliable: When we automate any application or process, the reliability is automatically increased to many folds. The major reason being less human errors.

Hey, check this out CSS caret-color: The “caret-color” property lets you set the background color of the caret in an editable text area.

How Automation Testing helps DevOps?

During the time when waterfall development processes were dominating all other development methods, all the different teams in an organization used to work independently. In waterfall technology, all the teams are laser-focused on their part.

Planning team plans the line of action
Defining team defines the various requirements and tools necessary to carry out that action
Then Production team builds the product according to the specifications
After building, the testing team performs the tests on the product to validate if it is meeting the requirements or not.
Then finally the product is deployed in the market for service.

This creates a lot of problems between the teams when it comes to finding a solution to some bug introduced at a certain phase. And it is next to impossible to locate at what stage the bug was introduced. But ultimately the main problem was that release to market in this development cycle was extremely slow. In an era where competitors release new features every other month, this methodology fails to give an edge.

This is where Agile technology came into existence. Agile technology follows the process of continuous development, continuous integration, and continuous deployment. In this technology, the product goes through different build cycles. Each build cycle includes production, testing, and feedback. This accounts for the need of DevOps.

In DevOps, Development and Operations teams work together to achieve the target. Since the product is tested at every build cycle so the testing needs to be in pace with the development process to avoid any hassle between the teams. DevOps can not succeed if the tests are performed manually as they consume a lot of time. So, here automation testing plays a major role. Automating a testing process decreases the time required for testing an application and it provides support to the DevOps culture. Without automation testing, it becomes almost impossible to practice DevOps.

Do you know about Case-insensitive CSS attribute selectors? In CSS, using an i after the]’ allows for case-insensitive matching. For example, [b=’xyz’] will match both <a b=‘xyz’> and <a b='xYZ'> .

When DevOps and automation testing work concurrently the following problems are eliminated:

Silos among the teams: Working together eliminates the differences among the teams and creates an atmosphere of understanding in the organization.
Delayed product deployment: Understanding between the teams increases the speed of product development and troubleshooting problems. As a result, the speed of product deployment increases.
Slower Release to market: If the product will be deployed at a higher frequency, then the problem of slower release to market will no longer exist.
High failure rate of new releases: When testing methods are automated and product is developed and tested in collaborative environment then the failure rate of new product releases will be decreased to a great extent.

Conclusion

In a nutshell, we can say that Automation Testing is a backbone to DevOps and it becomes impossible to implement DevOps culture without the help of Automation Testing. When practiced together in an organization, they can help to attain new heights of success.

Automating Acceptance Tests For Mobile Apps

deekshalt — Mon, 30 May 2022 11:21:16 +0000

From October 2016 to November 2017, Android released 4 major versions and iOS released 9 major updates. Its very good for users but it is problematic for developers and absolute hell for testers. One such problem testers face because of fast release cycles is Acceptance Testing.

So, if I say that mobile phone software are evolving day by day then you won’t disagree with me. Right? This evolution is, therefore, demanding for the fast testing methods so the end user gets the best experience. Acceptance testing, which is done to test the end user experience plays a major role in the success of Mobile Applications. Testers perform acceptance tests several times with every update in mobile software. With frequent releases, complexity of tests also increases. Hence automating these acceptance tests will ease the pain of the testers.

What Is Acceptance Testing?

Acceptance testing is the testing stage performed after the product has undergone thorough unit testing and service integration testing. In its essence, it is also the final integration testing, the testing stage where you integrate the whole solution to its final ready-to-ship stage. It is done to validate the final product and to check if it is acceptable for delivery or not. Therefore, acceptance testing is also called Business User Testing.

Acceptance testing can be broadly classified into two main stages:

Internal/Alpha Acceptance test- Done by the internal staff before releasing the product to the external customer’s use. Usually done in an offsite dev environment that is a replica of user environment. Sometimes for large applications, testing is performed by a pilot team of users along with dedicated testers.
External/Beta Acceptance test- Final testing done in the live deployment environment and also involves users of the application.

In both the stages, with every change in the operating system or software there is a need to test the software. So the testers need to perform acceptance test for every change frequently.

Hey, do you know CSS3 2D Transforms make elements spin, scale, move and morph into new shapes. Transform allows many attributes to be changed. Not only can you rotate and scale elements, you can also animate these transformations!

Why Automate The Acceptance Tests For Mobile Apps?

Traditionally automation testing is majorly used to speed up unit testing, integration testing, or system testing. In case of mobile applications, frequent updates in Android and iOS call for the need of frequent release cycles which require fast-paced acceptance testing hence the need for automating acceptance test. Automating acceptance tests also helps in regression testing because of their ability to test the complete product build and save a lot of time on final app-store releases.

Check this out, TTF/OTF — TrueType and OpenType font support- With support for the TrueType (.ttf) and OpenType (.otf) font formats in CSS3 @font-face, it’s easy to add professional quality fonts, in any weight or style, to your website designs.

What Do We Get Out Of Automating Acceptance Test For Mobile Applications?

When we automate acceptance tests for mobile applications we observe various benefits. Some of which are listed below:

Provides Continuous Validation

Acceptance test is done to validate the product, and automating acceptance testing helps to validate the app continuously. In an agile development environment that is following continuous integration and continuous deployment, we now don’t have to spend time on manually validating each mobile build. Therefore, it also speeds up the release of the product to the market by eliminating the need to keep a regular check on update. As when a new update is added it is automatically tested for acceptance.

Saves From Bad Customer Reputation

Customer satisfaction is the utmost priority when you are developing a product for them. We face various types of customers and every customer does not easily let go the faults in the product. So we need our product to be perfect for the user experience. Frequent tests from the end user perspective enhance the product quality by helping the developers to correct and identify more errors. So in the end, by automating the acceptance tests we can avoid any bad reputation in the market by delivering quality products to the end user.

Helps In Easy Accommodation Of Changes

Changes are inevitable and when it comes to mobile industry then they are inevitable and regular. So these regular updates need to be incorporated in the product. Automated Acceptance Test speeds up the end user testing hence this helps you easily embrace the changes by saving a lot of your efforts.

Do you know, Variable fonts now have independent control over the horizontal and vertical metrics that are used to layout glyphs from that font. This allows typographers to design a single font file that behaves like multiple fonts, providing all the variations needed for tasks such as typesetting.

Improves The Understanding Of The System

Automating acceptance tests increases the understanding of the system. Developers have claimed that writing unit or integration test scripts helps them understand the parts of the system but when they write acceptance test scripts they are able to understand the system as a whole. This also helps them to identify the loopholes( if there are some) in the application as they are able to understand what the system is meant to do rather than how it is doing it technically.

Testing A Progressive Web Application With LambdaTest

deekshalt — Fri, 27 May 2022 16:07:07 +0000

Developers have been trying to fully implement pure web based apps for mobile devices since the launch of iPhone in 2007, but its only from last 1–2 years that we have seen a headway in this direction. Progressive Web Applications are pure web-based that acts and feels like native apps. They can be added as icons to home and app tray, open in full screen (without browser), have pure native app kind of user experience, and generates notifications.

On the other hand, they take nearly no space, are fast, are reach like webapps, and eschews the whole process of update and release to change a feature or look and feel.

And they work offline!

As the name suggests, PWA or Progressive Web Applications are Web Applications… But better.

PWA are web applications that aim to provide an app-like experience to the users and have all the modern web capabilities all in one place. This technology provides all the app like functionalities directly from your browser and saves you from the pain of searching, downloading, and updating as in case of native apps.

Do you know CSS currentColor value is made to apply the specified color value to other CSS properties (background-color, color, etc.).

What makes an application a Progressive Web Application?

Right now based on research and content available on net related to PWA, Google is the highest authority. As per Google developer blogs and guidelines, if your app has the following features then you can say yes, my web application is a progressive web application.

Progressive: Your web app must work for every user, irrespective of the choice of the browser.
Connectivity independent: Yes, that’s what is one of the unsung heroes in a PWA. Your web app should work regardless of the internet connection or some of the features must work in no or slow network situations.
App-like: It should provide an app-like experience to the users. App like experience includes full screen mode, access to various in built accessories like camera, mic, etc.
Up-to date: Your web application must always be up-to the date and it should not bother the user asking for updates.
Safe: It should be served over HTTPS.
Easily Accessible: You can install the app or you can say access it directly from your homescreen with just one click on ‘Add to Homescreen’.
Fast: Reports show that 53% of users abandon your site if it takes over 3 seconds to load. And obviously you won’t want the users to go back. Hence, your app should be fast.
Responsive: As your web application is going to be opened in a browser then it should be responsive.

Once you’ve developed, it’s time to test!

Developing a Progressive web application is an altogether ball game and a little out-of-scope of this post. If you are intersted, Google has a great tutorial on it here. So once you are done developing a web application the next immediate step is to test it.

Check this out: ui-serif, ui-sans-serif, ui-monospace and ui-rounded values for font-family - With this extension, you can accurately set the font sizes and names of your system interface.

So, What all is to be tested in a Progressive Web Application?

While testing for a Progressive Web Application, you need to test for these given points:

Site is served over HTTPS: Safety is one of the major concerns in a Progressive Web Application, hence you need to make sure that your web application is served over HTTPS.
How to test? You can use Lighthouse by Google Developers, jitbit, seositecheckup, digicert,ssl shopper, ssl labs,etc to test if your website is served over HTTPS or not.
Web pages are responsive: Make sure that your web application shows a responsive behaviour across all mobile and desktop devices.
How to test? You can use LambdaTest’s responsive feature to test for your web app’s responsiveness.
Offline Loading: All your web pages or at least some of the web pages must work even when your app is offline. You need to make sure that your web app responds with a 200 when it is offline.
How to test? Again, since Google is massively pushing PWA ecosystem, they have some of the best tools for testing PWA apps. For example Lighthouse. Alternative is Wiremock.
Cross Browser Compatibility: You need to test your web app for cross browser compatibility to ensure that your web app gives a seamless user experience across all browsers.
How to test? You can use LambdaTest to test for cross browser compatibility testing.
Metadata for ‘Add to Homescreen’: You need to test if the web app provides a metadata for ‘Add to Homescreen’.
How to test? You can use Lighthouse to test for metadata for ‘Add to Homescreen’.
Page transitions should be smooth and shouldn’t feel like that they block on the network: Transitions are a key to perceived performance hence they shouldn’t feel snappy as you move around, even on slow internet connection.
How to test? This should be done manually on a slow network. When you click on any button or link it should immediately respond either by transitioning immediately to the nest screen and while waiting showing a placeholder loading screen or by a loading indicator till the app waits for the response.
Each page must have a URL: Every page on you web app must have a URL and all the URLs must be unique.
How to test? Test it by checking that every page is linkable by a URL and it is unique to be shared on social media or other platforms. The URLs can also be opened directly in new browsers.
Shareability: Content should be easily shareable even through full screen mode and it should form cards for all the social media platforms.
How to test? Test manually by sharing content from full screen mode. Test for cards can be done as:

Facebook: Debug the URL by entering the post to be shared and verifying if cards has been generated or not. Test it here.
Twitter: Check if the type of card for your content by is added to the given HTML’s HEAD of the page:

9. Availability of Schema.org Metadata wherever needed: Your webapp should be able to create a rich card if applicable. It helps to improve the appearance of your website by different search engines.
How to test? You can use Google’s Structured data to ensure image, description, title, etc are available or not.

10. Push Notifications: If push notifications are applicable for your web app they should not be overly aggressive.
How to test? Test the push notifications opt-in flow. There should be a clear instruction stating what the site wants permission for and why the user should enable the push notifications.

Watch this video to learn how to emulate network conditions in Selenium WebDriver by using the ChromeDevTools Protocol.

How LambdaTest can help in testing a Progressive Web Application?

Well, as I have already mentioned, Progressive Web Applications need to be responsive, browser compatible, and can be added to homescreen. How can you make sure that if your web app is fulfilling these criteria or not?

To your aid, with LambdaTest’s real time desktops, emulators, and simulators you can test if the web app you’ve developed is able to meet these. The next immediate question is how? Well, LambdaTest provides you over 3000+ mobile and desktop where you can test for this.

Adding to desktop or adding to homescreen can be tested if on adding my web app is showing the expected behaviour or not for that mobile or desktop?
Is my web app showing the responsive behaviour for every mobile and desktop?
Is the web app compatible with all the browsers and browser versions available?

Here, I’ve demonstrated how you can test for “Add to Homescreen” and “Add to Desktop” using LambdaTest.

Do you know gap property for Flexbox allows you to create gaps/gutters between flex items and to control the space between items.

Testing is done. What next?

Once you are done with the testing of your application, you’re left with the results if your web application is progressive or not. If not, go back and work upon it. If yes, then watch the conversions increasing as PWAs have proved to be a boon for the websites that have implemented it. The best examples are Alibaba.com, Aliexpress, Flipkart, and Lancome. After a short period of implementing PWA, Aliexpress has seen a major rise in conversions by 104%. Not bad?? So, what are you waiting for?

Machine Learning: If It’s Testable It’s Teachable

deekshalt — Thu, 26 May 2022 11:26:53 +0000

Ever wondered how you went to YouTube to watch just a 5 minutes video but ended up there for 3 hours? Or saw an advertisement on some page of exactly the same thing that you have been planning to buy for last 15 days and ended up finally buying it! Isn’t it great how your computer knows what you have been desiring? Well, it’s not your computer but the bots, the algorithmic bots that have been watching you all the time. Even now! Yes, that’s absolutely true. So the question comes, how these bots are made, and how software testing concepts come into play here.

It wasn’t very long ago when humans used to create algorithmic blogs that behaved like the real artificial intelligence. Simple and long code that basically said do this if this… or do that if that… for a while worked perfectly, and in many day to day activities it still works. However, as more and more people came on internet creating bigger and bigger datasets this approach simply didn’t work everywhere. Because some problems are just big enough to be taught by humans.

Let’s consider an example where you are shown two pictures one is of a dog and another is number 5 and you are asked what is what? Being an human you just know that yes, this is a dog and that is number 5 but how will the machine or the bots know?

We have to create a complex algorithm that will tell them to crawl the image pixel by pixel and find patterns in that picture that matches pixel patterns usually found in known dog images and give an estimated guess. Human brains have a complex wiring of neurons that learns every second. Similarly we will have to create complex bots with evolving pattern recognition intelligence which they develop over time as they keep learning.

Do you know CSS Shapes Level 1 allows you to create shapes with CSS, like rounded corners and circles. An area is defined and text can flow around this shape.

How Do They Learn?

Human programmers create a teacher bot and a builder bot who have simpler brains. Builder bot builds student bots and keeps and discards them based on their test grades.

The teacher bot himself cannot distinguish between a dog and a 5 but it can test student bots whether they are right in identifying or not. Now you get why automated testing is so important.

We give teacher bots a bunch of photos of dogs and 5s and an answer key of which is what. Based on this the teacher bot takes test of student bots and gives them the grades. Based on the test data, the builder bot keeps building on different student bots by adjusting different permutations and combinations of student bots algorithm mechanics, sometimes it even at random sees what sticks and what not. And the teacher bot keeps taking their tests and assigning them the grades. And the cycle continues.

The teacher bot keeps testing, and based on the grades of the student bots, the builder bot keeps the best performing bots and ruthlessly discards the rest.

The test, build, test cycle keeps on repeating in a loop and their grades are assessed and once the bot with approx 99.9% accuracy (or call them grades) is built the cycle is stopped.

Now the question that comes to our minds is ‘How many times the automated cycle of test, build, and test is repeated?’. Well, it repeats as many times it is necessary till the bot with the best grades is built. The best bot is the best algorithm to distinguish between a dog and 5.

Check this out CSS position:sticky: A lightweight polyfill which uses native CSS APIs to keep your “fixed” and “relative” elements stick to their desired position when the page is scrolled.

So What’s The Problem?

Now we have picked up the best algorithm to distinguish between a dog and the number 5 then what is the problem that may occur? If we give the bot a video of a dog or 5 upside down or letter ‘S’ instead of 5 will the bot still be able to figure that out? No.

How to Solve it?

To solve this, the humans have to create longer automated test cases with more number of questions for the student bots to pass, including even the wrong and the right scenarios so that it gets prepared for the worst cases too. Since longer tests ensures better bots.

As there is not a single bot or some ten or twenty questions but millions of bots and zillions of questions so how does the test, build, test cycle repeat? In that case you have to automate the process and keep on testing the same.

When a final bot is built it works and it is the only one which survives among the all as it is the only one whose algorithm was 0.01% better than the other bot. The algorithm that the student bot has built is not known by the teacher bot, not by the human overseer and not by even the student bot itself! It. Just. Works!

How the bot thinks or works, what it thinks is not really knowable.

Let’s come back to the YouTube example that we have discussed. We can understand this better now. The task here given to the student bots is to record the watch time of a user while keeping engaged and the student bot who keeps the user engaged for the longest watch time will score the highest. The teacher bots assess all the student bots and the student bots keep on giving recommendations to the users so that the user remain engaged. The one who gives the best recommendations and keep the user engaged is the one with the best algorithm.

Hey! Do you know CSS-Table is a library used to represent elements as tables, rows, and cells in a much more fluid manner.

Have You Come Across A Machine Learning Example Yet?

Believe it or not, we’ve all come across a real-time situation where bots have interacted with us using machine learning. Be it CAPTCHA collection, or customer care support. As a matter of fact, customer support is one area where machine learning has been adopted on wide scale by small companies and big enterprizes alike. We’ve all been aware of the constraints hanging around the customer chat support. You need to respond to customers in a jiffy and that can be especially tough for a global business who is aiming to provide 24/7 customer support as you need to make sure you have numerous representatives ready to help your customers all day & night. Fortunately, there are companies like Acquire’s chatbot which have helped numerous businesses amplify their customer experience by using their chatbots technology.

Which is the best example you could think of for machine learning bots? Let us know in the comments.

We’ve seen that the teacher bot is just testing the student bots and they are learning from the tests. So, in one line we can say that Machine learning is teachable if it is testable.

Common Bugs in User Interface Design

deekshalt — Wed, 25 May 2022 16:34:03 +0000

We’ve recently started our blog and with that came the need for various designing tools. For graphic creations we tested various image editing tools ranging from paint to photoshop. However nothing fared better than simplicity and productivity of Canva. We found it so interesting that we decided to dig further into it about how the tool can help you and what makes it stand out.

Creating a brand is difficult, and time consuming. Maybe that was the main inspiration behind Canva’s free design school. So we started out by checking out the school, went through some quick lessons, and were all set to carve out a brand, one image at a time.

Hey! Do you know the CSS page-break properties allow you to control the way elements are broken across (printed) pages.

Canva is free to join and provides a vast variety of templates and graphics. It has everything that you need for an amazing design. However here are the main features that will help you out as a starting blogger, web designer, or app developer.

Stock Images: You get access to millions of beautiful free and premium stock pictures, illustrations, and vectors. Saves you a lot of time in googling. Of course you can add your own custom images as well.
Filters everywhere: The fastest way to edit an image and leave your personal touch on it is by running it through a filter factory. And Canva comes with a lot of them. You can edit your pictures with the already available pictures or you can also modify them with the editor features.
Icons and Shapes: I know a lot of web designers who spent 30% of their time just designing shapes icons etc just to get that right branded feel across. But what if they get a collection of thousands of line and vector icons and graphics that can be edited easily? In short you get 30% more productivity.
Fonts : Typography can make or break a web design. Nobody thinks actively about it but we, web designers know how important it is in defining and presenting a unified brand experience across all platforms. It is the most important factor in your design that will leave a subtle yet lasting effect on all incoming traffic. A good font automatically catches the attention of the viewer. Canva offers a great selection of fonts for every design.

Check this out: ::placeholder CSS pseudo-element - The ::placeholder pseudo-element represents a hint used to represent the input and provide a hint to the user on how to fill out the form.

Social Media Experts, You Need Canva!

If you are a social media buff, or promoting a brand through social media, you need a lot of images. Banners, posts, thumbnails, insta, snapchapts, Google display ads, facebook ads, etc. each have different size requirements and meeting these requirements is time consuming. Here’s how Canva solves these problems:

Social Media Posts: It provides you with Twitter, Facebook, Pinterest, Instagram, Tumblr posts, covers, banners, thumbnails, headers and that too in their standard sizes. So you don’t need to worry about the dimensions and sizes. It removes barriers to your creativity. You can also add custom dimensions to your posts and images.

Ads: There are 20 different sizes in Google ads. Same with facebook ads. If you want to create a proper ad campaign, you need an ad for nearly each size. With Canva you can fast track this. We created ads for Facebook and Google, in different dimensions, all in a day.

Marketing Materials: You can also design your various marketing materials like Brochures, labels, posters, menu, logo, flyer, CTAs with canva.

Blogging & eBooks: Blogs and eBooks designing can also be done using Canva. You can also design Infographics and blog cover images. It provides tools that makes your designing easier like Charts, frames, grids, etc.

Do you know about CSS :read-only and :read-write selectors - the CSS :read-only and :read-write pseudo-classes allow you to match elements that are considered user-alterable, such as text boxes.

Canva Is Great For Web Designers, marketers, and artists.

Equipped with so many tools, Canva is an awesome tool for marketers, web designers, artists, and social media enthusiasts. We highly recommend checking it out and giving it a spin.

Common Bugs in User Interface Design

deekshalt — Tue, 24 May 2022 15:10:29 +0000

In human physiology, vision plays a major role as 83% of the information humans perceive is via sight. So, your website should never lack in visual appeal. In web design, this is even more important. Every new iteration of design leaves some minor deviations. Sometimes, these minor visual deviations can be very hard to fix or unknowingly break the whole user experience. Hence, it is necessary to make sure that your website provides a perfect and working interface design to the user.
So the question is, what are the factors that you have to lookout for while testing your website or app’s interface design? What are the most common bugs that are there and can go unnoticed?

So to make this easier for you we’ve collected some of the common bugs that can be encountered in user interface design.

Hey! Do you know the background-clip property lets you control where background images are shown, and the background-origin and background-size properties allow greater flexibility in the size of background images.

What are they?

1. Layout

Misalignment (eg: double margin float bug, staircase effect, IE6 box model bug, misbehaving floated layout, float drop bug, guillotine bug, IE resize bug)
Overlapping (eg: auto overflow)
Missing content/images
Spacing (eg: linewidth, line height, unwanted space between list items, vertical spacing bug)

2. Font

Font would be of same family but different type (eg: helvetica lite was the font but developer had put helvetica regular)
Fonts of different family used
Mismatching of font size

3. Color

Mismatch of colour code due to multiple reasons
Button colour should have changed when disabled but it got missed

Check this out CSS background-repeat round and space : It allows CSS background images to be repeated without clipping. Since it’s a property, it can be altered with CSS to reposition, distract, or focus attention.

4. Content

Upper/Lower-Case differences
Mismatch of letters/words
Mismatch of images
Spelling mistakes

5. Images

In certain browsers such as IE, sometime it is noticed that images tend to flicker. One of the reason being that browsers is unable to cache the background images properly and has to reload it again and again

These are some of the common visual UI bugs that sometimes go unnoticed by human eyes and therefore are very tricky to find. But you can be assured that out of thousands and millions end users that will visit your site, at least one will find them. Which is quite embarrassing, isn’t it?

So, in order to figure out these visual UI bugs before end users point them out, we’ve developed a special feature, Smart Visual UI Testing. This feature will allow you to compare images: Baseline image with comparison images in order to find all the visual UI defects with just one click.

Do you know CSS3 Border-radius (rounded corners) is used to create rounded corners on all four sides of an element’s border. It also covers support for the shorthand.

All you need to know about Blockchain Testing

deekshalt — Tue, 17 May 2022 11:28:26 +0000

From 2009, when Satoshi Nakamoto implemented blockchain technology as a core component in Bitcoin, blockchain has been the buzzword in the industry. Bitcoin’s success proved the capabilities of blockchain based transactions and and now everyone is planning to implement blockchain technology in almost everything. According to World Economic Forum survey, by 2027, 10% of the global GDP may be stored using none other than blockchain based technology. Interesting, isn’t it?

As you can see, from digital transactions to voting process, from storing documents and transactions to making data transfer decentralized, blockchain tech is going to be everywhere. So for developers working this space, here’s the main question, how do you know that your blockchain app is working just the way you want it work? In simple terms, how can you test blockchain?

First, let’s dive a little deeper into what exactly is blockchain technology, how it can help us, and what all needs to be tested in a blockchain.

Do you know the boolean async attribute on script elements allows the external JavaScript file to run when it’s available, without delaying page load first.

What is Blockchain Technology?

A blockchain is basically like a distributed ledger which stores the database of assets and transactions done across a peer to peer network. You can think of a blockchain as an open infrastructure that can store various types of assets.

Let me take this to a simpler level. Imagine you have to make a transaction of $10 from A to B. Now, in normal scenarios what happens is that transaction takes place through a third part app or payment processing system. First, A’s bank will identifying the details of B’s bank. Once that is done, then with the help of a payment processing service A’s bank will initiate a money transfer to B’s bank with a certain amount of deductions. Both banks will record transaction at their end. However a transaction fees is charged and B receives something like $9.95. This process is quite secure and have many redundancies in place to make sure that it stays secure and accurate, but even then there are some basic fundamental issues with the transaction process:

Delay in process
Dependency on a single intermediary whose effectiveness in never 100%
In case of any gap in the transaction, no one takes the responsibility and people keep on blaming each other.

Check this out, Spellcheck attribute — This enable/Disable the browser’s spellchecker on “input” and “textarea” fields for all forms with this extension.

How Blockchain eliminates these problems?

Consider if there is a system where you no longer have to worry about these problems faced. You just need perform a transaction and there are people who are sitting and validating your transaction every second. The validation mechanism is called as Proof of block and this is done based on the public key provided for the encrypted data, and it is done by all listeners in the peer-to-peer network. And these are real people, not bots. Since there is not a single transaction validating authority, i.e. no centralized transaction service, the process is effectively decentralized.

Once more than a specified number of people validates the transaction the transaction details are stored in the form of a block, and that block is added to the existing ‘blockchain’. Hence the name, blockchain. Moreover, the blocks once validated and added are immutable. These blocks have a specific hash associated with every block. These hashes are like fingerprints, unique to every block. The persons validating the transaction process are called as miners. More the number of miners, better the efficiency of transaction.

A block in all contains of data, a hash and a hash of previous block. Since it contains a hash of a previous block hence in a blockchain all the blocks contain data for the previous blocks so it becomes almost impossible for a blockchain to be corrupt.

So you can think of this as a distributed ledger where a lot of people are actively updating and validating your transaction details based on the decryption key that are provided. And once more than specific number of people validates the transaction a new block is added to the blockchain.

What is the need for testing in a Blockchain?

A block once added to the blockchain remains there forever and if you try to change the data in some block in between the chain, the following blocks become invalid. A single change in block of the blockchain will cause every subsequent blocks to change as well. This makes it important that whenever a new block is added, it’s being added the right way because it cannot be changed at a later date. It becomes complex to exploit a blockchain and the testing of blockchain becomes even more complex.
Add to that, it’s contributes to large transactions which goes through validation, encryption, decryption, transmission, etc so it becomes necessary to make sure that these processes go smoothly.

Check this out: Scoped CSS - Make your document easier to read and write by allowing CSS rules to be scoped to part of the document, based on the position of the style element.

What all do you need to test in a Blockchain?

Block Size: The maximum fixed limit of a block is 1 megabyte. After the introduction of bitcoin, the average size of a block for the first 18 months came out to be under 30 KB. But in December 2017, it hovered around 1 MB. What if the size of a block exceeds beyond 1 MB? Well, this is yet to be decided how the blocks above 1 MB pan out.
Chain Size: There is no limit on the size of the chain. So it is fun to test it for its function and performance. For example, the bitcoin chain’s size keeps on increasing day by day.
Load: With so many people on the blockchain, load becomes a major parameter to test in a blockchain. Let’s take an example of bitcoin. It currently has a maximum throughput of 3–4 transactions per second but what if the transaction/second increases as in case of Visa(2000), Paypal(193), etc. Hence load remains the major problem with blockchain as its performance drops when load increases.
Security: Since there are many miners involved with a transaction, ensuring security is a little complex. Well, there is a multi-layered security system in a blockchain. If one of the layers have been hacked, the instantaneous transactions cannot be stopped. It is therefore to be tested that one security layer doesn’t affect the other.
Transmission of data: Encrypted and decrypted data is transferred from computer to computer so it is necessary to test if the transmission process is working flawlessly. Is the data being sent received on the other end or there is a loss in between. So it becomes necessary to make sure that the data is not lost.
Addition of block: Every new block is added to the chain once the transaction’s validity is authenticated. So it must be tested that there should not be any leak in the block addition system and the block must be added after authentication.
Cryptographical data: Cryptography is the backbone of blockchain technology. So, it is necessary to make sure that the data is properly encrypted and decrypted.

This is just the beginning of the emergence of Blockchain technology. It has a lot more to show and teach us. We are going to see more of blockchain in the coming years with the pace it is taking over the technology world.

Cross Browser Testing Strategy Explained in Three Easy Steps

deekshalt — Mon, 16 May 2022 21:31:16 +0000

When you hear the term Cross Browser Testing what comes immediately to your mind? Something that decodes the literal meaning i.e. testing for cross-browsers or you can say testing an application across various browsers.

But it’s not as simple as it sounds.

Cross browser testing in itself is a whole different ecosystem and requires a lot of planning and prerequisites before you decide to go ahead with that.

In this post, I wanted to dig deeper into cross browser testing process focusing on efficient strategies using which you can cut down on the time and effort required for your high impact cross browser testing.

Objectives Of Cross Browser Testing

Before delving deeply into cross browser testing, we must be aware of what are the objectives we want to achieve through our testing process. Cross browser testing in summary serves the following two purposes:

Discovering bugs: This involves breaking your application by various ways in order to find the bugs.
Sanity Check: This involves making sure that your audience receives the same experience across various platforms.

I would say to meet your two objectives you can plan your testing in two ways.

One, cover most used browsers by your target audience first and test for outlier browsers later. For example, if I want to test for sanity check for US audience targeted product, I would test my website on latest versions of Chrome, Safari, and Firefox, and I’ll cover over 50% of my audience in these three browsers. Assuring compatibility across these three browsers alone assures me of the majority of the audience in US.

Two, if I want to find out bugs in my application I can just throw it to the most problematic browser and check for any bugs.

This is a general case but if my application is getting updated regularly then how I am gonna go for cross browser testing?

Well, in that case I can have one of the following three criteria.

Ignore the bug
Fix it and hope that the updates haven’t broken anything
Fix it and test it again for all the browsers again.

The third case is the ideal case for any organization but doesn’t the process seem to be tiresome and lengthy?

Yes, it does. So let’s figure out what we can do to perform cross browser testing with less efforts such that it creates maximum impact on the application.

Do you know Indeterminate checkboxes are used in hierarchical checkboxes to indicate that only some of the checkbox’s descendants are checked. They are distinguished by a gray or dimmed background and lack a border.

Cross Browser Testing In A Restaurant

Doesn’t this seem a bit of unusual? Well, no!

Let me explain how?

Consider you are a restaurant chain owner planning on to introduce a whole new dish into the market. You’ve been working on that for quite a long time and you don’t have a damn clue on what it is going to be like when it is gonna be released into the market.

You, of course, have put your heart and soul into it and you just want to deliver it with the utmost perfection. So. how is this gonna work out?

Level 1: Development: You’ll prepare the dish and first check for yourself if everything is in place or not. Once you are satisfied with that you’ll go to the next level.
Level 2: Controlled Testing: Variety of people have variety of tastes and suggestions. So, you’ll go for a quick variant check by trying in your local restaurant. You would test you new dish in an controlled environment, serve it to chosen set of customers, and get constant feedbacks to improve it further.
Level 3: Testing in Production: Once you feel that different variants of people have accepted your dish then you can further expand it and add it to the full menu at your chain restaurant’s menu as well, one restaurant at a time. You still take regular feedbacks on the new dish though, finding ways to improve it.

Same is the case with cross browser testing. You put your heart and soul into developing your web app or website and again you want to deliver it with perfection. So in order to deliver your web app or website into the market you need to do through these three levels of cross browser testing. You start by developing the app itself with a specific purpose, target audience, and device type in mind.

Then for level 2, you test your app in an controlled environment on most readily available browsers, or on browsers that you largest percentage of audience is using. In final step, you test your app on all possible browsers your audience use to access your app, so that your web app or website works flawlessly for every platform it is opened.

Do you know you can test Fomantic UI Web Apps Online — A high performing cross browser testing and cross device testing cloud for at scale Fomantic UI testing.

Getting Started With Cross Browser Testing

Before deciding for performing cross browser testing you need to do a lil bit of homework on the user data, what is that is liked by the users in that specific area, what they uses the maximum, demographics study, and so on.

Assume if the dish that you’ve been trying to release is a non-veg dish and the users in that particular area are mostly vegetarians then there will be strong chance of poor performance.

Similarly, if the users in an area uses chrome by 85% majority then there is an affinity towards testing for its perfection on chrome. No matter what you cannot afford any bugs on chrome. So, you need to figure this out on highest priority. You can check out this infographic on some of the browser statistics that can help you in figuring out the mostly used browsers on mobile and desktops.

Also, analytics tool like google analytics are a great help in analyzing user behaviour especially in finding out what type of browsers your users are using to access your website. 😉

Once you are done with the data study, it’s time to move up to the three levels and reaching the third level is what we are aiming at.

The Three Levels In Cross Browser Testing

The First Level: Exploring Bugs

Wanna test the dish yourself first? Go to the first level.

Once you develop a website/ web app you need to test it for bugs on your local browser by running possible test scenarios which can cause your website to break like:

Check for breakpoint
Check for app behaviour with JavaScript turned off
Check for zoom in and zoom out
Check the website using only keyboard navigation
Check for page load script

These bugs are browser specific as you are checking them in a specific browser and figuring out the possible defect scenarios in a specific browser.

You need to very careful while fixing a bug that you don’t introduce more bugs while fixing the already existing ones. So, after fixing you need to make sure of not introducing the bugs in the previous version so you have to again test it for all the cases.

The Second Level: Strategizing

Once done with the first level, you need to move to the second level which involves moving on to the variant testing. Now in this level you need to act smart, else everything is gonna messed up.

You have already identified browser specific bugs. It’s time to start testing it across different browsers.

Strategize your testing to take it to minimum effort, high impact level.

Analysis of bug distribution Classify your browsers based upon the risk associated in three zones.

a) High risk browsers
b) Medium risk browsers
c) Low risk browsers

Now analyze your bug based upon these three divisions of browsers. The major aim here is to cover all the bugs with fewer iterations of testing rounds.

Say, you have the following scenario where the bugs introduced in various browsers are denoted by ticks here.

Now there are two ways: Either start from low risk browsers and go to high risk browsers by fixing bugs or start the other way around. Recall, our main aim is to cover all scenarios with fewer iterations. So, if we start fixing from high risk browsers by fixing Bug1, Bug 3, Bug 4, and Bug 5 then there may be a possibility that you don’t need to fix Bug 4 in medium risk browser.

When you fix bug 2 in medium risk browser, the tendency of bug 2 staying in low risk browser becomes negligible. So you need to fix 5 bugs and perform 6 rounds of testing on all the bugs.

‘Eliminating the bug in high risk browser automatically decreases it’s chances of being present in low risk browsers’.

So, you have to carefully analyze the bug.

2- Identify problematic browsers: As I have already mentioned, fixing bugs in high risk browsers is what you need to start with so you need to figure out the most problematic browsers and make your code compatible with these browsers. This will decrease your efforts and less problematic browsers become easier for you to handle.

Now you may ask what is a high risk browser?

Well, the answer comes out to be really tricky depending upon the browser features that your application is using. Like:

If your Javascript uses ‘indexOf’ there is a chance that it may break in IE 8.

How to find which is a high risk browser for me?

The answer to this question is : You can use Can I Use tool to figure out browser compatibilities for various technologies.

The Third Level: Sanity Testing

Once you are done with finding and fixing bugs in the second level it’s time to finally move to “THE THIRD LEVEL’ i.e. sanity testing.

Testing at this level is like 80:20 rule. For me it goes like

‘80% of the browsers contains 20% of the bugs and the rest 80% of the bugs will show up in the remaining 20% of the browsers’.

So you need to now test those 20% of the bugs for finding and fixing those 80% of the bugs.

So where are you going to start?

Again, strategy and a bit of common sense plays Ace of Spades here.

Do you know, the Date and Time Field Widgets add different input types to the field widgets for easily allowing users to enter a date, time or both. The calendar widget lets the user pick a date and display it along with a month and year picker in the popup window.

Browser Prioritizing

Start testing by prioritizing the browsers based on the relevance of the browsers and then going on to the least relevant browser. Makes sense, right?

If your audience is using Safari the maximum then you need to test it for safari first. Then followed by the browsers which are the least used.

This is basically done in the descending order of market share.

What’s the point of testing your webapp on the browser which is being used by 0.05% of the population? So, your testing needs to make sense here.

Based on browser prioritizing decide for yourself, which browsers makes the most sense to you and which browsers makes the least sense.

Go back to level 2. Follow the same procedure based on bugs specific browsers on the basis of high, medium, and low risk browsers and get ready to see your dish getting appreciation from every single person.

This is how you can achieve a level of perfection for cross browser testing in minimal efforts creating high impact.