Nowadays, it seems the new title for software testers is either Software Development/Design Engineer in Test (SDET) or Software Engineer in Test (SET) or similar. The emphasis is on the evolving skills of a tester having the capabilities to develop (or code) meanwhile advancing their techniques of applying best practices in test automation. This makes sense when we consider how the multitude of frameworks for development web application and software tools has also evolved.
Here are some articles to read.
Evolution of the Software Testing role:
- https://www.test-institute.org/Software_Testing_Roles_And_Responsibilities.php
- https://learn.org/articles/How_Does_a_Software_Testing_Engineer_Do.html
- https://www.softwaretestingclass.com/what-is-difference-between-sdet-and-tester/
- https://www.ness.com/significance-of-a-software-development-engineer-in-test-sdet-in-the-digital-economy/
- https://www.cigniti.com/blog/rise-of-the-software-development-engineer-in-test-sdet/
- https://www.guru99.com/software-developer-engineer-test-sdet.html
- https://testing.googleblog.com/2011/01/how-google-tests-software.html
- https://testing.googleblog.com/2011/02/how-google-tests-software-part-two.html
- https://www.testing-whiz.com/blog/8-software-testing-trends-every-tester-should-follow-in-2018
- https://www.upwork.com/hiring/for-clients/top-5-emerging-software-testing-trends-follow-2018/
One can also gain an understanding of what a test engineer (or SDET or SET) does today by looking up the job qualifications on major tech company career websites including Google (specifically "Test Engineer"), Amazon (spec. "Software Development Engineer in Test"), Microsoft (spec. "Software Design Engineer in Test").
A Quick Recap from Microsoft's Personal Experience
Here's a nice recap from Microsoft on the transition of eliminating the Software Test Engineer (STEs) and creating a "combined engineering" team.
Software Test Design
Similarly to developing any software, developing scripts to test software also should go through the design phase in order to create test structure. This helps with organizing tests to correspond to the software design, finding bugs early in the design process of software development, creating a testing framework for easier ramp-up of new Test Engineers and for easier review of the software development team, and more.
Software Test Design - Problems
First problem I'm interested in is what to name the appendages of the class files especially for the automated test scripts via the browser.
Unit Tests use the appendage "Test" like "HelloWorldTest".
Integration Tests use the appendage "IT" like "HelloWorldIT".
I've seen throughout the Selenium docs the term "AUT" (or application under test) and wonder if I should use this as the appendage for my test scripts via browser like "HelloWorldAUT". But is this sufficient?
Software Test Design - Research
https://dzone.com/articles/design-patterns-in-automation-testing
What is SOLID (Principles)?
- Single responsibility
- Open-Closed priniciple: open for extension and closed for modification
- Liskov substitution
- Interface segregation
- Dependency injection
https://msdn.microsoft.com/en-us/magazine/dn683797.aspx (dated: May 2014)
*There are a number of terms explained in this article that I really like. For instance, the author says "when I say principle, I'm referring to a feature of the computer code that helps maintain the value of that code."
Software Testing Conferences
Here are some conferences to be aware of with respect to software test automation and the future of testing software.
Software Test Tools
There are a lot of tools from the many articles online that I've read. Not to overwhelm one with reading through all the articles and also knowing that the software tool depends on the software developed, here's a short list of tools that I'm learning and applying.
Leading the list is Selenium as the best, open source tool for testing web applications.
- Selenium - https://www.seleniumhq.org/docs/
I should really keep track of my progress here. This is getting way too long. So I need to split this step into smaller steps and start publishing.
No comments:
Post a Comment