Normally unit tests were written by developer who write the code, i.e. Test Driven Development.
So what does Software Engineer in Test do?
|
Normally unit tests were written by developer who write the code, i.e. Test Driven Development. So what does Software Engineer in Test do? |
|||||||||||||
|
|
Short answer: SETs (or SDETs as we call them at MS) test well beyond what can be done by unit testing (integration, performance, scale, reliability, etc.), and write programs, tools, and automated tests to aid in the effort. The role is quite similar at Google. Longer answer: I've written about the role (both directly and indirectly) on my blog. Start with this post on careers, or search the site for SDET. Longest answer: Read my book. |
|||
|
|
|
I currently work as a sort of SET (although my job designation is still SE). What I do mainly is to create unit tests and load tests for the finished application (or almost finished) in addition to those made by the people actually coding on it. Depending on the app I am testing, it involves the creation of unit tests, automated UI tests, and writing various test scripts to interact with and test the application. Often this involves the use of one or more test tools/frameworks and a small amount of coding. |
|||
|
|
|
They write code to test Software Engineers' code. A lot of times they develop automated test tools. AFAIK, Google, Microsoft and other big software companies hire a lot of SETs. Test engineers utilize three types of testing strategies which are known as black box, white box and gray box testing. |
|||||||
|
|
That is what I currently do. I focus on being the Other Guy, the Adversary who stands in for the customer and tries to break the code. I write piles of functional tests and supporting libraries. |
|||
|
|