Skip to main content
replaced http://sqa.stackexchange.com/ with https://sqa.stackexchange.com/
Source Link

I am in no way trying to be rude, but I think the hiring team may be setting themselves up for failure. Having worked on many many automation projects and worked with many people of varying skill levels, it is actually just about impossible for someone with no automation background to jump in to automation and get it right the first time. With no guidance or mentoring from someone more senior who has done it before, you will be left to figure things out, which I am sure you will be able to do... over the course of many years. In the meantime, you may get some automation up and running and it will likely add value, but may have any number of problems like being un-maintainable, unreliable, or not really validating what you want it to validate or what is important to validate.

If it were my decision as a hiring manager, I would absolutely make sure the first person I brought in had prior experience writing automation.

With all of that said, this very well could be a great learning opportunity for you, and here are some answers that may help on the Selenium side:

Good resources/tutorials/tips for beginner doing automation?Good resources/tutorials/tips for beginner doing automation?

Manual tester wanting to get into automationManual tester wanting to get into automation

Your suggestions for writing reliable Web UI automationYour suggestions for writing reliable Web UI automation

For JMeter, honestly you can figure out how to use the tool by looking through documentation and examples, but the far more important thing for performance testing is understanding HTTP inside and out. You need to understand how app servers like IIS and Tomcat work, you need to understand the architecture of your applications and know how they interact, and know what to monitor while executing your load tests. You need to know what requests are important to validate, vs what you can fire and forget.

Here are a couple of links that may also be useful for performance testing with jmeter: http://jmeter.apache.org/usermanual/intro.html

https://www.packtpub.com/books/content/functional-testing-jmeter

How to determine breaking point of my application when performance testing from jMeterHow to determine breaking point of my application when performance testing from jMeter

Best of luck.

I am in no way trying to be rude, but I think the hiring team may be setting themselves up for failure. Having worked on many many automation projects and worked with many people of varying skill levels, it is actually just about impossible for someone with no automation background to jump in to automation and get it right the first time. With no guidance or mentoring from someone more senior who has done it before, you will be left to figure things out, which I am sure you will be able to do... over the course of many years. In the meantime, you may get some automation up and running and it will likely add value, but may have any number of problems like being un-maintainable, unreliable, or not really validating what you want it to validate or what is important to validate.

If it were my decision as a hiring manager, I would absolutely make sure the first person I brought in had prior experience writing automation.

With all of that said, this very well could be a great learning opportunity for you, and here are some answers that may help on the Selenium side:

Good resources/tutorials/tips for beginner doing automation?

Manual tester wanting to get into automation

Your suggestions for writing reliable Web UI automation

For JMeter, honestly you can figure out how to use the tool by looking through documentation and examples, but the far more important thing for performance testing is understanding HTTP inside and out. You need to understand how app servers like IIS and Tomcat work, you need to understand the architecture of your applications and know how they interact, and know what to monitor while executing your load tests. You need to know what requests are important to validate, vs what you can fire and forget.

Here are a couple of links that may also be useful for performance testing with jmeter: http://jmeter.apache.org/usermanual/intro.html

https://www.packtpub.com/books/content/functional-testing-jmeter

How to determine breaking point of my application when performance testing from jMeter

Best of luck.

I am in no way trying to be rude, but I think the hiring team may be setting themselves up for failure. Having worked on many many automation projects and worked with many people of varying skill levels, it is actually just about impossible for someone with no automation background to jump in to automation and get it right the first time. With no guidance or mentoring from someone more senior who has done it before, you will be left to figure things out, which I am sure you will be able to do... over the course of many years. In the meantime, you may get some automation up and running and it will likely add value, but may have any number of problems like being un-maintainable, unreliable, or not really validating what you want it to validate or what is important to validate.

If it were my decision as a hiring manager, I would absolutely make sure the first person I brought in had prior experience writing automation.

With all of that said, this very well could be a great learning opportunity for you, and here are some answers that may help on the Selenium side:

Good resources/tutorials/tips for beginner doing automation?

Manual tester wanting to get into automation

Your suggestions for writing reliable Web UI automation

For JMeter, honestly you can figure out how to use the tool by looking through documentation and examples, but the far more important thing for performance testing is understanding HTTP inside and out. You need to understand how app servers like IIS and Tomcat work, you need to understand the architecture of your applications and know how they interact, and know what to monitor while executing your load tests. You need to know what requests are important to validate, vs what you can fire and forget.

Here are a couple of links that may also be useful for performance testing with jmeter: http://jmeter.apache.org/usermanual/intro.html

https://www.packtpub.com/books/content/functional-testing-jmeter

How to determine breaking point of my application when performance testing from jMeter

Best of luck.

Source Link
Sam Woods
  • 8.6k
  • 25
  • 43

I am in no way trying to be rude, but I think the hiring team may be setting themselves up for failure. Having worked on many many automation projects and worked with many people of varying skill levels, it is actually just about impossible for someone with no automation background to jump in to automation and get it right the first time. With no guidance or mentoring from someone more senior who has done it before, you will be left to figure things out, which I am sure you will be able to do... over the course of many years. In the meantime, you may get some automation up and running and it will likely add value, but may have any number of problems like being un-maintainable, unreliable, or not really validating what you want it to validate or what is important to validate.

If it were my decision as a hiring manager, I would absolutely make sure the first person I brought in had prior experience writing automation.

With all of that said, this very well could be a great learning opportunity for you, and here are some answers that may help on the Selenium side:

Good resources/tutorials/tips for beginner doing automation?

Manual tester wanting to get into automation

Your suggestions for writing reliable Web UI automation

For JMeter, honestly you can figure out how to use the tool by looking through documentation and examples, but the far more important thing for performance testing is understanding HTTP inside and out. You need to understand how app servers like IIS and Tomcat work, you need to understand the architecture of your applications and know how they interact, and know what to monitor while executing your load tests. You need to know what requests are important to validate, vs what you can fire and forget.

Here are a couple of links that may also be useful for performance testing with jmeter: http://jmeter.apache.org/usermanual/intro.html

https://www.packtpub.com/books/content/functional-testing-jmeter

How to determine breaking point of my application when performance testing from jMeter

Best of luck.