Manual tester wanting to get into automation

  • So its been a year since I have been studying Python, and just recently I started picking up web driver. It was a long journey, and I am still a pretty noob, but I finally understand how to use it lol. I have made some tests to automate my manual testing, which took a long time, but worked!

    I am wondering what kind of tests QA automation engineers make daily. I made simple ones like logging in, creating a ticket, creating alarm, verifying other stuff. I can see it getting complex, but in general, am I ready to apply for an automation job? I don't want to look like a fool and say "hey I made a script to login!", but I honestly have no idea what kind of work an automation engineer would do. I can only assume it's similar to what I am doing now, and that it seems pretty basic.

    My goal was to learn some Selenium, so that I have SOME automation experience, and put that on my resume. I feel I can automate a lot of what I do with WebDriver, but it wouldn't exactly be efficient, just mainly good for experience. Do any automation jobs not mind finding a novice that they can teach? Or will most require someone who can do everything right off the bat. Would be nice if a QA automation engineer can respond with what kind of tests they write and what level they would require, thanks!

  • All the learning starts from step1. You have learned based on your own interest. I had a lot of support from this community and StackOverflow when I started writing automated tools. I can share my experience. 5 Rules for beginners getting into test automation:

    Rule#1 - Do not worry about design, error handling when you start writing your automation suite. Write pieces of functionality and integrate it slowly. Refactoring, Applying OOPS principles, logging can be learnt once you get your code working.

    Rule #2 - If you want to write selenium automation follow, select recommended tutorials / articles in this forum. There are a lot of resources you need to select and read good info articles. A mentor, in this case, would be of great help.

    Rule #3 - Explore Tools - Focus on learning TestNG Basics, JUNIT basics, SOAP UI and other tools. Divide automation into multiple layers - Framework Design, Execution Layer, Logging, Reporting Layer. Allocate time and try out freeware tools, GTAC talks, Tools demo sessions.

    Rule #4 - Ask for help if you are stuck. Ask for help on best practices, approach design in forums. Accept your mistakes and learn from them, keep improving your knowledge continuously.

    Rule #5 - Review your own framework based on below guidelines:

    1. Re-runnable - All tests are re-runnable without any hard-coded / static data not used.
    2. Do not repeat your code/duplicate code, re-use same methods whenever needed (you are applying OOPS here).
    3. Results Reporting - Results are readable, able to drill down the steps of each test case.
    4. Error logging and reporting - You have the option to enable/disable logging to different levels to debug issues.
    5. Configurable - Able to run the system against any environment with minimum configuration changes.
    6. Apply Design Patterns / OOPS Principles / Best Practices and Keep Improving your Automation Suite.

    Hope it helps!!!

    Using an existing automation tool QTP, Winrunner most of the items reported will be taken care of by the product itself. Primary work would be recording, writing cases.

    Developed a mature in-house automation framework takes several iterations but working code is always best to ship it, to begin with.

Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2