DEV Community

Discussion on: Best Automated Testing Tools for 2020

Collapse
 
razgandeanu profile image
Klaus

I have mentioned only solutions that also provide cross-browser clouds.

That was one of the items from my list of requirements.

What can I do if part of our users are using Internet Explorer 11 and Safari?

Collapse
 
istvandesign profile image
Istvan Fulop

Platform is not everything, for instance I highly doubt you'll even touch iframes or shadow dom with endtest. Did you try to test a table with 1000 elements and virtual scroll ? What about a table in a canvas ? Maybe test that the data in a table is the same as in the database or backend or that formatting and styling for instance is valid for every cell. How do you do that if you can't code in a real language ?

Would endtest still be the best tool ? Most likely it wouldn't even be able to read anything on the page in any enterprise app.

I checked your other articles, you clearly plug in endtest in every article. In my opinion endtest is basically useless for anything else than static or very simple apps, prove me wrong.

Not trying to troll, but I don't like it if my favourite platform is getting full of promotion without merits.

Thread Thread
 
razgandeanu profile image
Klaus • Edited

Hi Istvan,

Those are some good questions.

Let's take a look at the Documentation.

  1. You asked about iframes and Shadow DOM.
    As you can see in the Finding elements in Web Applications chapter, this tool supports both.
    You just need to use the "Switch to iframe" and the "Switch to Shadow DOM" actions.

  2. You asked about canvas elements.
    As you can see in the Dealing with Canvas Elements chapter, this tool can deal with Canvas elements.

  3. You asked about connecting to a database and performing a SQL query.
    As you can see in the Execute SQL queries chapter, you can easily connect to a database and perform SQL queries.

  4. You asked about testing the styling.
    As you can see from the Assertions for Web Tests chapter, you can add different assertions, including Element Contains CSS Class, Element Contains Attribute, etc.

And to make sure that it looks as expected, you can add Screenshot Comparison steps.

And if you want to verify a long list of elements, you can just add a loop.

You can even add a CSV file and loop through the rows and generate variables from each row and use them in a test.

I never make statements about a library or a tool before reading the Documentation.

You should do the same.