Switching From Manual Testing to Automation testing in my new workplace

🙋 Questions
, ,
1

Get the most out of asking a question.

  • Is the topic title a question? No
  • Does the topic title include a “question mark”? No
  • What are you asking of the community?

Hey yall, so i been working at this startup in India for last 4-5 months, its just me and my lead here, so our management had a word with us and stated to start automation testing in our website,

so our frontend is : Angular + react + vue.js
Backend is: java+python+go lang
Database: mongodb, sql and MySQL
Devops: Azure, we have around 4 websites i think , our appstore, partnerstore,back office and our platform, not exactly sure which all use which all languages, has a vague idea,

They are kind of migrating everything to Go, in our Backend as well.

So we first decided we will go with Robot framework with python as it’s relatively easy to use and play with

We have written some 4-5 test cases for now and intergrated it into azure ci/cd pipeline so that it runs as a job every day at 20:00 , we are confused on what to do next or how to proceed? As it’s relatively a small startup , should we proceed with robot framework itself, I have written around 7 regression tests , which we are planning to incorporate to the CI/CD pipeline, so that everytime a new build happens it runs

  • How can they help you? Confused about how to go ahead with as me and my lead are relatively noobies in automation testing
  • What context can you share to increase the likelihood of someone replying to your question? I don’t know whether this is the right place to ask questions
3 Likes
2

I guess this question was too broad

1 Like
3

Instead of going forward, I’d go a step back.
Evaluate if you need it, when you need it - now or later, where it fits in the process, which type of automation, what resources are needed and for what goal, if there’s training needed to be quick, what will suffer if automation is done, what will be gained.
Others:
What is the current testing strategy?
Is there a reasonable confidence in the assessment of the product?
Could there be more resources needed to test appropriately? or a different process? as you get the product a few days before release?
Is there automation in the product elsewhere? unit, integration? API? What are developers automating already?
Which type and scope of automation is appropriate and what will it help with?
For automation, how many resources do you have in the testing role? how about helpers(devs)?
What would you have to give up to automate?

1 Like
4

Just like @ipstefan mention above. I think you need to think through some basic test strategy for the whole project or at least discuss these topics thoroughly during your ceremonies (refinement, planning, whatever
).
Possibly, try to also observe what’s going on with the test suite itself - how stable it is, how to maintain it, who maintains it.
It looks like you jumped into the conclusion of having full end to end tests (I suspect this is what these tests do) instead of actually checking what you’ve been currently doing and how well or badly you’ve been doing it.

1 Like
5

As you move forward with the setup at your startup, think about not just testing, but also how your team collaborates and manages changes. For example, setting up a clear process for how changes are reviewed and merged can really help to run things smoothly with your CI/CD pipeline and automate some of these processes.

Consider how you manage your workload. Maybe break tasks into smaller, manageable parts, change your QA processes, and set regular meetings to discuss progress and any problems. In your situation, it’s important to avoid getting overwhelmed.

Your focus is on testing and tech, don’t forget about the bigger picture like user feedback and dev process, team resources management, communications with stakeholders, etc.

6

It looks like you are explaining your situation but i still dont get what help do you need?

Can you be specific please?

7
  • I read it as a question regarding the right automation plan to approach in their context.
    “Confused about how to go ahead with as me and my lead are relatively noobies in automation testing”
    More granular:
  • What to automate(‘We have written some 4-5 test cases for now, on what to do next or how to proceed?’)
  • What to automate with: ’ should we proceed with robot framework’
  • when, how, which scope, what layer: ‘our management had a word with us and stated to start automation testing in our website’
8

Yeah, I guess its a lil bit too early to start automation testing in our company.

I guess we probably have to start with UI and functional automation tests and smoke regression tests .

Resources, I think : its just me and my lead here now, we should get more trained in the language we are selecting,

I think Regression tests would be a lot more quicker to execute as its automated instead of doing manual tests everytime

What is the current testing strategy? Our Current strategy is purely manual testing, Where if it is a new feature, we write the test cases and try to execute them and then run the smoke regression tests every time manually, Currently, I have written around 10-12 regression test cases, which we run every day as a job , we plan to make changes so that every time there is a push to the main code, We branch and run the tests against the latest code , but we don’t plan to do it now

Is there a reasonable confidence in the assessment of the product? I wouldn’t say we are quite confident with the product ,

Could there be more resources needed to test appropriately? or a different process? as you get the product a few days before release? : I think, we should rethink the whole testing approach, as our team doesn’t have any clues regarding automation testing , Yes,we do get the product , a 2-3 days before the release,if its a major feature, we get it a week or 2 weeks ahead

Is there automation in the product elsewhere? unit, integration? API? What are developers automating already? Currently, I don’t think there is any automation going on, I asked my developers, and they ain’t writing any unit tests or anything in their language, Will try to check with them, whether developers are automating anything already

Which type and scope of automation is appropriate and what will it help with? we are literally clueless on what to do going forward

For automation, how many resources do you have in the testing role? how about helpers(devs)? Its actually just the two of us testers right now in our current team, I think we would be able to bring around at least 2 developers

What would you have to give up to automate? : I don’t think we would need to give up anything

9

yeah, actually we did jump into it too early, I think, Its kind of end to end tests

I think we would need to possibly rethink the whole testing stategy, but we are kinda confused, on how to start automation testing

I guess i would be maintaining it, its not that stable, but okayish

10

Yeah, I think we should, have a clear idea on how changes are reviewed and merged , cause we are doing it randomly now, we do the changes and do manual testing and then pass the build is what we are doing

I wish and I think we should change our QA process, but literally confused on what to do , as its purely manual testing right now

11

Ooh sorry my bad, its just me and my lead here in our company for QA’s, and we are clueless on automation testing and we wish to implement it in our process and start it, we are curious on how to start ?