Those looking to break into the test automation field have difficulty doing so because of lack of experience. One way to gain experience is, of course, to study and practice on your own. But how do you demonstrate your newfound knowledge to employers?<\/p>\n\n\n\n
Other professionals, such as front-end developers, create portfolios to highlight their skills, and you can do the same as automation engineers!<\/p>\n\n\n\n
Here are 10 projects for your test automation portfolio that will help you stand out among the competition.<\/p>\n\n\n\n
Web automation is by far the most common and sought-after form of test automation. If you’re looking to break into test automation, this is an absolute must-have for your portfolio.<\/p>\n\n\n\n
Be sure to go beyond a basic login flow. Instead, show full scenarios that require your code to interact with multiple pages.<\/p>\n\n\n\n
This project should demonstrate your ability to find element locators<\/a> and interact with various types of elements such as dropdown menus, checkboxes, text fields, buttons, links, alerts, file upload widgets, and frames.<\/p>\n\n\n\n Also, be sure you’re writing clean test code<\/a> and utilizing design patterns such as the Page Object Model<\/a> or the Screenplay Pattern<\/a>.<\/p>\n\n\n\n Sites to practice against:<\/strong><\/p>\n\n\n\n The demand for mobile test automation engineers has increased over the years as the popularity of mobile apps has soared. Having experience here can certainly work in your favor.<\/p>\n\n\n\n Your portfolio should demonstrate automated testing against both iOS and Android apps. Using Appium<\/a> to create one project that works for both iOS and Android would be great. Using tools such as Apple’s XCUITest<\/a> or Google’s Espresso<\/a> is good as well. But if you go this route, I recommend doing at least two projects (one of each), since each supports only one mobile operating system.<\/p>\n\n\n\n No matter which framework you use, you’ll want to demonstrate the same element interactions as you did in your web automation project, but also mobile-specific gestures such as swiping and pinching.<\/p>\n\n\n\n Apps to practice with; download any of these to use in your project:<\/strong><\/p>\n\n\n\n After making your web and mobile projects, fork them and add visual testing<\/a> capabilities to them. You’ll quickly see just how much your tests are missing because they weren’t enabled to verify the appearance of your app.<\/p>\n\n\n\n Visual testing is a skill being listed on a number of job postings<\/a>, and having this skill will really help you shine against the competition.<\/p>\n\n\n\n With the rise of microservices, IoT applications, and public-facing APIs, the demand for automation engineers who know how to test APIs has become substantial. So definitely add an API testing project to your portfolio. (Here’s a free class on how to test APIs<\/a> to get you started.)<\/p>\n\n\n\n Within this project, be sure to demonstrate a variety of API methods, with GET and POST as a minimum. Use APIs that require parameters or request bodies, and also return complex responses with multiple objects and arrays.<\/p>\n\n\n\n For bonus points, use advanced verification techniques such as deserialization<\/a> or approval testing<\/a>. Also, demonstrating how to mock API responses<\/a> would be a nice bonus.<\/p>\n\n\n\n APIs to practice against:<\/strong><\/p>\n\n\n\n Many teams are practicing behavior-driven development (BDD) and automating tests based on the specifications produced. You’ll want to demonstrate your experience with this and how you can jump in and hit the ground running.<\/p>\n\n\n\n For this portfolio project, be sure to not only show the mapping between feature files and step definitions<\/a>, but also demonstrate how to share state between steps via dependency injection<\/a>.<\/p>\n\n\n\n Also, be extremely careful when writing your feature files. Long, verbose feature files will hurt your portfolio more than help. Make the effort to write good, concise Gherkin<\/a>.<\/p>\n\n\n\n Your practice projects may use only a small amount of test data, so it’s easy to store that data inside the source code. However, on production development teams, you’ll have hundreds or even thousands of automated tests. To keep up with all this data, many teams adopt a data-driven testing approach.<\/p>\n\n\n\n I recommend adding this to at least one of your projects to demonstrate your ability to programmatically read data from an external source<\/a>, such as a spreadsheet file.<\/p>\n\n\n\n Speaking of being able to access data from external sources, it’s a good idea to add a project that interacts with a database. I recommend writing queries within your code to both read and write from a database, and use this within the context of a test.<\/p>\n\n\n\n For example, you can read from the database to gather the expected results of a search query. Or you can write to a database to place your application in a prerequisite state before proceeding to test.<\/p>\n\n\n\n Writing all of your portfolio projects in one programming language is okay; however, automation engineers often need to dabble in multiple languages.<\/p>\n\n\n\n To make yourself more marketable, try using a different language<\/a> for a few of your projects.<\/p>\n\n\n\n Also switch it up a bit and try a few other automation libraries as well as assertion libraries. For example, maybe do a project with Selenium WebDriver in Java<\/a> and JUnit, and another project with Cypress<\/a> in JavaScript and Mocha.<\/p>\n\n\n\n I know this sounds daunting, but you’ll find that some of the architecture and design patterns in test automation are universal. This exercise will really solidify your understanding of automation principles in general.<\/p>\n\n\n\n Automating accessibility testing has always been needed but recently has become extremely important for companies. There have been legal battles<\/a> where companies have been sued because their websites were not accessible to those with disabilities.<\/p>\n\n\n\n Demonstrating that you are able to do test automation for accessibility<\/a> will give you a great advantage when applying for jobs.<\/p>\n\n\n\n You can use the same sites\/apps you used for your web and mobile projects to demonstrate accessibility testing.<\/p>\n\n\n\n Last but not least, you should consider adding a performance testing<\/a> project to your portfolio.<\/p>\n\n\n\n Nonfunctional testing such as performance is a niche skill that many automation engineers do not have. Adding this to your portfolio will help you be perceived as a unicorn who really stands out from the crowd.<\/p>\n\n\n\n GitHub<\/strong><\/p>\n\n\n\n Be sure to put all of your projects on GitHub so employers can easily access and review your code. However, be careful to hide secret keys<\/a>. This will give you bonus points, since it shows another level of maturity.<\/p>\n\n\n\n Website<\/strong><\/p>\n\n\n\n Create a website that highlights each of your portfolio projects. You don’t have to build the website yourself; you can use common CMS systems such as WordPress to allow you to quickly get your portfolio up and visible.<\/p>\n\n\n\n Each project highlight should include a paragraph or bullet points explaining what you’ve done in the project and the tools and programming language used.<\/p>\n\n\n\n Resume<\/strong><\/p>\n\n\n\n Include a link to your portfolio on your resume, and feel free to list your portfolio projects under the “Experience” section of your resume.<\/p>\n\n\n\n While this is not traditional work experience, it shows that you are self-driven, passionate, and competent to break into the test automation field.<\/p>\n\n\n\n Interview<\/strong><\/p>\n\n\n\n During your interviews, be sure to mention all of the projects you have worked on. Draw from your experiences with building the projects to be able to answer the questions. Also brush up on other concepts around testing and development<\/a> that may come up during the interview.<\/p>\n\n\n\n Good luck!<\/p>\n\n\n\n <\/p>\n\n\n\n The original version of this post can be found at TechBeacon.com<\/a>.<\/p>\n\n\n\n Header Photo by Shahadat Rahman<\/a> on Unsplash<\/a><\/em><\/p>\n","protected":false},"excerpt":{"rendered":" Angie Jones describes a portfolio of ten projects that help even novice test engineers demonstrate their skills to get the job. <\/p>\n","protected":false},"author":31,"featured_media":25011,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[12271],"tags":[10199,12494,10031,16620,10061,10103,12686],"acf":[],"yoast_head":"\n2. Mobile automation<\/strong><\/h2>\n\n\n\n
3. Visual automation<\/strong><\/h2>\n\n\n\n
4. API automation<\/strong><\/h2>\n\n\n\n
5. BDD specification automation<\/strong><\/h2>\n\n\n\n
6. Data-driven automation<\/strong><\/h2>\n\n\n\n
7. Database usage<\/strong><\/h2>\n\n\n\n
8. Multiple languages and libraries<\/strong><\/h2>\n\n\n\n
9. Accessibility automation<\/strong><\/h2>\n\n\n\n
10. Performance testing<\/strong><\/h2>\n\n\n\n
Presenting the Portfolio<\/strong><\/h2>\n\n\n\n