I think you got your base assumption wrong, DevOps is not a silo skill and profession that you either have or not, belong to or don't.
Knowing how to use AWS cloud, Docker, Kubernates or Google cloud is something you will use as a test engineer even before you start developing automation.
Is it mandatory ? obviously not, but you and your career will greatly ...
It looks like you need to perform a stress test
Example steps I would take:
Assess which network protocol(s) is(are) in scope, i.e. how the streaming is implemented
Choose a load testing tool which support this(these) protocol(s)
Implement test scenario by replicating the network footprint of the real user using a real browser (or an application) listening ...
I found the solution to this myself. For anyone who's having the same issue:
What I did wrong was I used driver = new ChromeDriver(options); in my code instead of driver = new RemoteWebDriver(new URL("http://my.aws.ip:4444/wd/hub"), options);
After making this change, I downloaded selenium-server-standalone.jar to in EC2.
Then, before starting the ...
From your question I see that you want to make a smoke test on a production system. Testing on production could be very risky in some scenarios. So there are few questions that you should analyze:
Do you change the state of the system accessed only with specific
user or they will be available to all prod users? If the data is
available to prod users for me ...
I like to answers questions with questions during interviews.
My first response would be that the question "How to test AWS?" is very broad.
My first question would be: Which part of AWS should I test?
As of 2020, AWS comprises more than 175 products and services
including computing, storage, networking, database, analytics,
application services, ...
I did a Cost-Benefit-Analysis a few years ago (so take it with a grain of salt) and found
AWS Device Farm - Worked really well for Android but didn't screen record iOS runs and the remote control mode was really laggy.
Xamarin Cloud - Worked well but was expensive and instrumenting was a chore. I don't recall a remote control mode.
TestObject - Had ...
There are two issues you need to think about;
You are running on headless mode, so there should be no visible Chrome window. You may need to disable it.
If the Jenkins initiated the job; you can see the Chrome window, only if you VNC with Jenkins user, not another account/user.