Automation testing interview preparation

Interview tips

  • Current role and resposibilities – Tools used are cucumber, groovy, Maven + Java, RestAssured, Appium, Bamboo, Docker, C#.Net + Specflow. Responsibilities include automation of new tickets + Maintainance of tests on Bamboo and Cross browser testing on browsers and mobile devices
  • Strong qualities / Points – skills in hot technologies like UFT, Jira, Selenium, Appium, AWS, Docker, Cucumber + Collaberation. So right fit for the role + Work ethics + Flexibility + Commitment + Honesty and Integrity + Adaptability (New tech stack)
  • Weak qualities / Points – Communication and presentation
  • Challenges faced – Domain knowledge, False positives and negatives, Technical issues in selenium like staleElementException, Synchronization issues, Not everything can be automated, Missing Requirements, Weak Processes with respect to jira tickets in teams, Cross browser challenges, Dependency on devops for setting up AWS agents and Bamboo configuration
  • Achievements – Docker and Selenium, Production tests with Selenium and integration with Slack, Inhouse set up of Appium and iPhone testing, Tech blogs and books, Restassured framework implementation, Cucumber BDD implementation, Contribute to open source project on GitHub
  • Automation testing benefits – quick time to test, continuous integration, Accuracy, Regression testing through automation can save lot of time and resources
  • Automation testing drawbacks – not everything can be automated, false negatives, Initial investment, Maintainance, Skills

Manual testing concepts

  • Software development models – Waterfall, Iterative (After each iteration, the product may not be in usable state), Spiral (combination of waterfall and iterative), V shaped (Testing and development in progress), Agile (requirements keep changing, Minimum viable product as soon as possible)
  • Scrum is an agile, iterative, incremental framework for managing product development. Scrum has timeboxed iterations. Each iteration is called as a sprint and may take a week to month. Everyday there are standup meetings and they are called as daily scrums. In scrum, there are mainly 3 roles – product (Business) owners, scrum master and development team. Roles of scrum master is to manage the sprint process and not people (unlike project manager). Scrum framework involves sprint planning, daily scrums, sprint review and retros.
  • Sprint board vs Kanban board – Kanban board is used for maintainance type of project where the work is not planned. Kanban is a lean method.
  • Testing levels or phases – Unit testing, Component, Integration, System, UAT (Acceptance testing), Alpha beta testing
  • Test approach – static, dynamic, blackbox, whitebox, grey box, regression, Smoke test (Build verification test. Generally done before build is given to testing team), Sanity testing (quick tests of critical features and advantage is that we get quick feedback)
  • Test techniques – Compatibility testing, Exploratory Testing, State Transition Testing, Boundary Value Analysis, Equivalence Partitioning, Usability, Accessibility, Security testing, Performance testing
  • Defect lifecycle – new, assigned, open, fixed, restest, closed
  • Priority and Severity of the defect – 
  • Test artifacts – Test plan, Traceability matrix, Test case, Automated test script and suite, test data, test report
  • IEEE 829 test plan structure – Test plan (Test strategy is a wider term) includes items like resources, budget and timelines, objective, scope, Process, tools to be used, Test plan identifier, Introduction, Test items, Features to be tested, Features not to be tested, Approach, Item pass/fail criteria, Suspension criteria and resumption requirements, Test deliverables, Testing tasks (test priorities, test execution and generating reports), requirement traceability matrix, ROI, Environmental needs, Responsibilities, Staffing and training needs, Schedule, Risks and contingencies, Approvals
  • Metrics – Code coverage, Bugs per line of code,  ROI
  • Automation project steps – POC, Test plan, Test automation framework, Application knowledge and training, Automating the tests, Integration with CI servers, Maintainance

Automation testing Concepts you must know 

  1. UFT – Object repo vs Descripting programming, UFT vs LeanFT, UFT vs Ranorex
  2. Jira – Sprint vs Kanban Board, Jira Workflow, Integration with Version control system, Agile vs Waterfall models, Using code feature to style the text, Epic vs Ticket, Writing filters, Configuring boards and dashboards, creating projects
  3. GIT and GITHUB – Cloning repo, How to commit, pull and push changes, How to resolve conflicts, How to revert the changes, How to view changes, Git branching models, Working on Github, Creating pull requests, Reviewing changes and approving pull requests
  4. Cucumber – Hooks and cucumber options for rerunning failed scenarios, generating reports, tagging scenarios and running specific tags with AND, OR, XOR combination, Gherkin, BDD
  5. Difference between testng and junit – When to use JUnit and TestNG, Various annotations, Creating test skeleton
  6. Difference between maven and gradle – What are the pros and cons of both tools, maven phases and goals, Maven profiles, Maven repo, Maven plugins, View dependency tree
  7. Linux and powershell commands – All important linux commands, Frequent linux tasks that can be automated, Writing shell scripts, Profiles, Shell variables, User variables, Package managers and Installations, Vagrant, Difference between Desktop, VM, vagrant and Docker
  8. Appium vs Selenium – How appium is different, Page object models
  9. Appium on Mac – Running tests on iPhone, iPad simulators
  10. AWS, Bamboo and Docker – Creating EC2 instances and configuring it with docker, bamboo agent process and running tests on it, Bamboo tasks for AWS plugin, Deploy plugin, Teamcity and Jenkins
  11. Jmeter – How to use Jmeter to do performance testing, HTTP config element, Extracting data from JSON responses using JSON extractors, Extracting data from response headers, Using HTTP header elements, Creating thread groups, Generating reports using report elements
  12. Java – core OOPS concepts, Classes vs Interfaces, Generics, static and singlton, multi-threading, collections, Serialization and Reflections, Casting objects and type conversion, Final vs Static, Utility classes, Regular expressions, Useful libraries e.g. apache common, Mustache, Springboot and Database handling, Input and output, File handling
  13. C#.Net – Build management tool – MSBuild, Package management – Nuget, Important namespaces and classes, Data types and type conversion, OOPS concepts, Strings, Regular Expressions, File handling, Collection and Generics, Anonymous methods, Properties (getters and setters),
  14. Javascript – Objects and classes in Javascript, ECMAScript Versions, Javascript frameworks, DOM vs BOM, Events, Apply, call bind, this object, closures, Hoisting variables, including js files in other file
  15. IntelliJ – Tips and shortcuts in IntelliJ IDEA
  16. SQL – all important sql queries, joins, finding unique and duplicates, sql functions, triggers and procedures
  17. Protractor – How to write and execute tests in protractor, Javascript test frameworks
  18. Rest endpoint testing – RestAssured, Postman, SoapUI
  19. Security testing
  20. Optional things  –  Groovy, Python, Ansible, React and Node.js, NPM, Spring boot, Tosca, TestComplete

Structure of Interview in Australia

  • Apply on or or or LinkedIn or References and contacts
  • Full time vs Part time
  • Permanent vs Contract based – No leaves, no job security, low work life balance but high salary usually stated as daily rate ($400 to $1000 per day)
  • Recruitment agency vs direct HR engagement – Direct HR contact is always preferrable as it is a faster way to secure the job. But 70% jobs come through agencies so you should be ready.
  • Ask them to schedule the interview early in the morning so that you will not have to take sick leave. After interview, you can go and work in your current company so that no one will doubt that you are looking out for a job. Do not tell anyone in the office that you are actively looking for job. This may put you in trouble.
  • Aussie Accent and Listening practise – For people with no western accent and listening experience, it can be very difficult to clear the interview. So practise listening to western music and movies. Also be very attentive and listen carefully. If you did not get the question, you can say “Pardon me” or “Say that again” or “Sorry can you please repeat your sentence” or “Can you please speak slowly” or “Can you please rehrase the question”
  • No of rounds depends on company. Most of the times, you will need to visit the company office twice. First for HR round and second for Tech interview or other way round. But some people manage to get a job in single visit as all rounds are planned on the same day.
  • Your job Referee – You should be ready with 2-3 referee. Your team leader or manager can be your referee. Make them aware about possible verification call from the HR department.
  • Interview Panel may contain 2-3 people
  • Questions will be based on the roles and responsibilities, Strong and weak points, Best qualities a team member or leader should have, why we should hire you, tools and framework, main challenges, achievements
  • Negotiating salary – You are not obliged to tell new employer about your current salary. It is your choice.
  • On first day of job, submit documents like TFN, Superannuation details, Signed Contract etc. You usually go through induction on first day. Car parking is provided but it is not free. They usually charge $100 per month for the covered parking
  • Notice period – It is counted in weeks and not in months. Most of the companies have notice period of 4 weeks.
  • Probation period is usually 6 months and during probation they can fire you. If you want to resign during probation, notice period is usually 2 weeks but again depends on each company.
  • Personal / Sick leaves vs Annual leaves – Sick leaves will not be carry forwarded to new year. Most of the managers will not ask for the medical letter if you take a sick leave.
  • Work hours – Official working hours are usually 8:30 AM to 4 PM. I have not seen anyone working on weekends or after hours.
  • Annual parties and other milestone parties – Parties are typical western style with hollywood music and lots of beer. Indians usually do not like the food in parties as veg options are minimal and in non veg, there will be options like beef/pork/ham/ bacon/chicken/fish. Strange thing is that even waiters will not be able to tell you the ingredients of the food. I have lot of friends who have eaten beef/pork burgers thinking that it will be a chicken berger or veg berger. That’s a terrible experience. So you need to be very careful.