CSS & Markup: Few Testing Tips You Probably Are Missing


2 m read


Tips & Tricks, Web Application Testing

We have encountered a new project last Friday, and, since it was Friday, we went out after work. What do you guys usually talk about when you should be chilled and relaxed and happy to have free personal time? Well, whatever it is you are doing, we always get back to work-related matters. I can’t really say why, but we are constantly into work as a team. If we have what to test, we discuss it 24/7, and if any product was launched and we have some spare time, we talk about how we tested it. I am probably getting carried away, though. Where were we?

Oh, yeah, right. Our new project was PSD to HTML conversion for a well-known media agency I’m not allowed to name here, and it involved a lot of CSS testing and we have already had a round of beers so we could not avoid the temptation and began discussing some really efficient ways of testing. So, during our little friendly discussion we began to go deeper and came up with several astonishing ideas I am really willing to share here with you guys. They are not everything you must know about CSS testing, nor do they involve the entire process. These are simply several things that are often overlooked:

  • First of all, mixing content and layout is probably a bad idea and can cause lots of security breaches after user input. Same may happen if HTML tags were placed inside any single element. Potential risks like this should be of the first rational things you are to test. How to know if there is any of this fishy mixing? If things like ‘FooBar”.html_safe or any other analogies were used you have a red light blinking bright and clear!
  • Check for bare text. It must not be present without appropriate containers. Any text that has either left his container or had none from the start may and will be affected by even the slightest styling changes. And who knows what this may cause?
  • Developers tend to stuff as much divs as possible when CSS layout is used. This way layouts are achieved easier, I get it, but come on! The product will eventually grow in size and all that weight will not cause any good effect on rendering and load speed of the page. Less divs is always better, and you, as a tester, have a nice spot to check for defects.
  • The last, but not least – content and layout are different things and styles differ from them even more. Yet developers love mixing a nice little cocktail of tags and style blends and this, in turn, leads to chaos. Do not repeat their mistakes. Threat these 3 pieces differently and have 3 different practices you will use when testing starts.

This discussion has made our Friday fascinating and improved our web service testing a bit. How did it affect your day?

Realizing the importance of providing service on agreed terms, we consider all possible risks and provide efficient solutions for all possible risks and provide efficient solutions.


We use cookies to ensure your best experience. By continuing to browse this site, you accept the use of cookies and "third-party" cookies. For more information or to refuse consent to some cookies, please see our Privacy Policy and Cookie Policy