If you ’ re a developer, you may not think that package testing has much to do with you, or that you have much to do with package testing.

But cerebrate this way is sell yourself short. It ’ s true that traditionally, package examination has been the focus of QA engineers who are devote to the office of ensuring that software behaves and performs as required to meet user expectations. As more and more administration make the displacement toward automated examination, however, the skill sets of exam engineer are increasingly overlapping with those of developer.

Why? Because in order to take advantage of automated testing, you experience to write automated test code. QA engineers don ’ t typically specialize in coding, but developers do. So, if you ’ re a developer, it ’ s likely that you have much to offer to colleagues who are compose machine-driven exam. It ’ s even possible that you ’ ll be asked to play a role in writing machine-driven test.Both types of work offer an opportunity to make yourself more valuable to your governance, especially in the present DevOps-centric age, where quislingism and teamwork are key to deliver software efficaciously.

All of the above means that if you ’ re a developer, now is a full time to educate yourself about the basics of software testing (if you get not already), so that you can be most helpful in pen the tests that your governance needs to assure software quality. Toward that end, this article provides a primer on package testing from a developer ’ s point of view.

What is package testing?

To start with the near introductory (and obvious), here ’ s a definition of software testing: Software testing is the process that assures that an coating meets user outlook.

That ’ s a uncomplicated way to put it. There is more that could be said about what user expectations mean, and how you mensurate them. But sooner than center on that issue, the almost crucial thing to proceed in psyche is that the end-goal of software testing should be to delight exploiter. If you ’ re focused on your users, success in other areas will follow.

Types of package testing

Software tests descend into many different categories. The most basic is unit try, with which you ’ re probably already familiar as a developer, because it ’ s something that typically happens shortly after codification is publish.

Other forms of testing, like execution testing, usually occur later in the development cycle, and you may not have much to do with them as a developer. But if it ’ s your finish to assist in package testing, you should acquaint yourself with them.

Why automatize testing?

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

Automated testing is a hot topic in the world of software testing and QA today. By let organizations to write programs that perform various tests on a software application automatically, rather than requiring human technologist to execute and monitor examination manually, automated testing enables much faster and more scalable tests. (It besides tend to save your organisation a lot of money.)

Given the priority placed by many DevOps teams today on being able to deliver package continuously, as well as achieve scalability, automated testing has get the goal that many organizations reach for.

This do not mean that every single software test is automated—that ’ s rarely the case at most companies. Certain tests, such as usability tests involving existent, live users, are best performed manually. Overall, however, test automation present the best, fastest upshot in most position.

How do you write an automated test?

To write machine-controlled tests, you demand two basic things.

The first is an automated testing fabric that supports the type of covering you need to test.Seleniumis a popular general-purpose choice for web covering.If you ’ re examine for mobile, you ’ ll be best function by a program like Appium(which is based on Selenium but designed for wandering testing).

The second thing you need is automated test codification. The lyric in which you write your code will depend on which automated testing framework you use. The major frameworks support near democratic languages. Selenium, for example, works with C #, Java, Perl, PHP, and Python.

If you ’ re a programmer, writing test codification itself is relatively simple. It ’ s basically just script, and yet the longest automated testing hand tend to lie of merely a few hundred lines of code.

Of course, if you ’ re a QA engineer with slight or no coding experience, pen these kinds of tests could be intimidating. That is why, as a developer, you can offer a great heap of value by assisting with automated tryout development.

How and where are examination executed?

If you ’ re a developer, you may not have much visibility into how software trial are actually run. After all, your main focus is on write codification, not testing it.

But as most QA engineers can recite you, test execution usually happens on base that is set up specifically for screen. Servers are provision expend emulators or simulator that create environments that mimic those in which an application will run in production, and the covering is try inside those environments.

In order to speed up testing, it ’ s common to use what ’ s called a test grid, which is essentially a cluster of machines that host test. Using a test grid, you can run multiple tests at erstwhile — or, in former lyric, run tests in parallel — in order to get results quicker.

You can set up test infrastructure on your own on-premises ironware, but when it comes to software prove (like so much else), it ’ s common these days to take reward of the cloud. When you use cloud-based exam infrastructure, you don ’ t have to worry about pose up and managing your own servers to support your tests. Plus, cloud-based testing can be handy in position where you need to run tests on a specific type of physical hardware device (such as a particular mobile sound) but don ’ t own that device yourself.

Conclusion

Your chief job as a developer may be to write code. But because publish code is now an important part of software testing, it ’ s hard for developers to ignore the work that QA engineers do to test software. By teaching yourself about how software testing works and how you can assist your organization make the leap to test automation, you can earn props for yourself, while too make the overall software delivery pipeline flow more smoothly.

Chris Riley (@ HoardingInfo) is a technologist who has drop 15 eld help organizations transition from traditional evolution practices to a modern set of civilisation, processes and joyride. In add-on to be an industry analyst, he is a regular author, speaker, and evangelist in the area of DevOps, BigData, and IT. Chris believes the biggest challenges front in the tech marketplace are not instrument, but rather people and preparation.