ui test automation best practices you should follow

20
UI Test Automation Best Practices You Should Follow

Upload: infocampus-bangalore

Post on 23-Jan-2018

52 views

Category:

Education


1 download

TRANSCRIPT

Page 1: UI Test Automation Best Practices You Should Follow

UI Test Automation

Best Practices You Should Follow

Page 2: UI Test Automation Best Practices You Should Follow

In this, will total and characterize the top best practices

for making a strong and viable UI testing mechanization

system. Let’s go over some convenient cases for each of

these standards.

Page 3: UI Test Automation Best Practices You Should Follow

Try not to depend ONLY on

UI test automation:-

Page 4: UI Test Automation Best Practices You Should Follow

One of the principle best practices you ought to consider at first

- don't depend on UI test mechanization alone. In a perfect world, you

ought to be certain that in the event that you evacuate your entire UI

robotization suite from the test cycle, you will have the capacity to make

up for lost time to 90% of existing bugs in your discharge.

You generally need to recall that abnormal state tests ought to

be just the third guard shield, for finding all the rest of the issues that

were not gotten on the initial two levels.

Page 5: UI Test Automation Best Practices You Should Follow

To start with, low-level tests are substantially quicker by nature.

Unit tests are speedier than API tests while API tests are considerably

quicker than UI tests.

Why is this critical? For the most part, on the grounds that

speedier tests give you quicker input. Speedier input from tests

execution enables you to get issues at an opportune time, sparing you

immense measures of expenses.

Second, low-level tests are executed significantly before in the

QA computerization pipeline. For the most part, unit tests are keeping

running before each submits in your archive.

Page 6: UI Test Automation Best Practices You Should Follow

On the off chance that this is valid for your undertaking, at that

point you can even say that you don't just catch yet you counteract bugs

and don't give them a chance to get into the task store. Obviously, this

likewise spares you a considerable measure of expenses.

Third, low-level tests are substantially steadier than abnormal

state ones. When some person asks me for what valid reason I incline

toward all the more low-level tests in my test robotization structures

Page 7: UI Test Automation Best Practices You Should Follow

Consider utilizing a

BDD structure:-

Page 8: UI Test Automation Best Practices You Should Follow

What is BDD?

BDD is a product improvement strategy in which programming

is actualized in the way its conduct is depicted. You can begin from this

wiki page in the event that you have never found out about this system.

BDD can be connected for a testing including unit tests, segment, and

combination and also for some, different sorts.

UI testing is one of the principle ranges where BDD can be

connected with an incredible achievement. BDD is suggested for UI

Automation, for some reasons.

Page 9: UI Test Automation Best Practices You Should Follow

Above all else, BDD is a system that enables groups to see

each other, making solid outside and inside group cooperation. By

composing your tests with BDD you likewise make particulars that can

enable your group to comprehend tests and prerequisites much better.

This implies alongside composing your tests, you are making a

reasonable tests documentation. This guarantees you don't squander

other colleagues' chance (who may take a shot at your tests later), and

your own chance, since you don't have to clarify and help with such

tests on the off chance that they are hazy.

Page 10: UI Test Automation Best Practices You Should Follow

Continuously dependably

ALWAYS utilize test configuration

examples and standards:-

Page 11: UI Test Automation Best Practices You Should Follow

An outline design is a reusable answer for a typical issue in

programming plan. We can state that each example is a specific case of

a particular answer for a particular issue, paying little respect to the

programming dialect or worldview.

Supplementing configuration designs, we have outline

standards. Plan standards give you rules or decide that you have to take

after for developing admirably manufactured and viable programming.

While designs apply for particular issues, outline standards apply paying

little heed to setting.

Page 12: UI Test Automation Best Practices You Should Follow

UI testing is a hard and tricky street loaded with various

openings. Be that as it may, I have uplifting news for you. You are not

the main driver to travel this street.

That is the reason there are no gaps nobody has ever gone

through. You can consider configuration examples and standards as

effective pilots.

Page 13: UI Test Automation Best Practices You Should Follow

NEVER utilize Thread.sleep()

unless there are particular test

prerequisites:-

Page 14: UI Test Automation Best Practices You Should Follow

This is a brilliant decide that you have to take after paying little

respect to the multifaceted nature of your web application. Rest or

correct timeout hinder your test string for a correct determined number

of seconds. At the end of the day, it gives you the capacity to stop your

tests. At the point when might you need such ability?

The conduct of web applications relies upon many variables like

system speed, your machine capacities or the present load on

application servers. In view of every one of these components, you can't

generally anticipate how much time it will take to stack a particular page

or web component.

Page 15: UI Test Automation Best Practices You Should Follow

Try not to run ALL tests over ALL

objective programs:-

Page 16: UI Test Automation Best Practices You Should Follow

The principle thought of this decide is that running all tests

against all objective programs is excess and superfluous. We have to

plainly comprehend what we will accomplish by running our tests

crosswise over various programs. The fundamental objective of this

activity is to perform program similarity, to confirm that application works

accurately on every bolstered program.

Page 17: UI Test Automation Best Practices You Should Follow

UI test computerization isn't flimsy. The security of your UI test

computerization system is just up to you.

Genuine, steady and solid UI mechanization is diligent work, but

on the other hand it's entertaining. You have a decision toward the start

of your system creation: would you say you will utilize a device that will

enable you to achieve your objective and comprehend your issues, or

will you make programming that you will battle with again and again on

consistent schedule?

Page 18: UI Test Automation Best Practices You Should Follow

Infocampus is one of the institutes that provide selenium training in Bangalore, marathahalli. In infocampus, selenium course will be provided with less training fee and also placement assistance is provided.

It is a best selenium training institute in Bangalore. Classes are more emphasized on practical.

Contact 9738001024 or enquire on http://infocampus.co.in/best-selenium-testing-training-center-in-bangalore.html for more details on Selenium Courses in Bangalore and also book a seat for free demo classes on selenium.

Page 19: UI Test Automation Best Practices You Should Follow
Page 20: UI Test Automation Best Practices You Should Follow

Visit Here…

Infocampus Training Institute,

1st & 4th Floor, Above HDFC Bank,

Near Kalamandir,

Outer Ring Road,

Marathahalli,

Bangalore-560037