Some people like to build things. Some people like to break things. Really special people like to break abstract things like software, using software.
At SPR, our agile software development projects demand ever-greater efficiency in both development and testing activities. Growing a software product iteratively and incrementally means there are thousands of opportunities for defects to enter a code base. Clean coding practices and test-driven development help. A lot. But developers are builders. Project teams need breakers, too. And great teams need great breakers
A great breaker at SPR (a Software Development Engineer in Test) is someone who...
- … is a great software developer. Someone who knows OO, one or more curly-brace languages, and knows how to use an IDE efficiently for Java or C#
- … knows databases. Someone who can produce SQL SELECT statements with correlated subqueries on demand. Someone who knows what name-value pair and document databases are all about
- … knows about web services, and REST API’s, how to call them from test code, and how to parse JSON and use assertions to confirm that they work properly. Someone familiar with tools like RestAssured, Postman or SoapUI
- … is fundamentally lazy. Someone who hates doing the same thing twice, let alone 50 times, and who therefore is passionate about automation
- … is someone who likes doing things right. Who likes knowing that a test framework will run reliably, build after build, consistently point out defects, and never throw “false positives.”
- … has an interest in mobile application development, and an ability to dive in and learn new automated testing tools for iOS and Android platforms. Someone familiar with Appium or other mobile automation frameworks
- … knows how to set up and execute functional tests against web applications. Test that expose real problems, but which are resilient enough to keep working when cosmetic changes are made to the app being tested. Someone familiar with tools such as Selenium Webdriver
- … is organized. Someone who knows that for defects to be fixed, they need to be in someone’s work queue. Someone familiar with tools like JIRA, Lighthouse, TFS and HP QC
As an SDET at SPR, you’ll be asked to