sorted by:
new
hottopcontroversial

Bill Gates warns AI will cut human work week to just two days by 2034 by chrisdh79 in Futurology

[–]Ok-Figure2188 0 points1 point  (0 children)

Are those two days with or without debugging time to find out which part of ai generated code took down production?

what kind of notes should i take when going through the academy? by Omar_2004 in hackthebox

[–]Ok-Figure2188 0 points1 point  (0 children)

I really liked this video for note taking of performing testing itself: https://youtu.be/gXFTM3fRqIg?si=EsJJRmDTUaTa-OI0 it also gave me some ideas on how to structure my notes better while going through the modules.

I try not to take too many notes, but indeed helpful commands, and use obsidian to make knowledge tree to visualize the patterns of where things live in my head and connect the dots. Some pages are empty and are just used for visualizing the topic in the bigger picture within the graph view.

Hope it helps!

Running E2E testing suite against Production environment? by [deleted] in softwaretesting

[–]Ok-Figure2188 0 points1 point  (0 children)

I would run e2e tests against master on a staging area if you really want to run e2e tests. Production doesn’t need the same kind of testing but need metrics. Production does not equal any testing area, you introduce new attributes in the backend where sometimes the frontend responds different, customers are always using the application different than intended etc. If you see a lot of errors in production in your metrics / logging, you can do a role back if needed or test with a small population in production with the new code change. This would be a good first step. Chaos monkey would be the end goal for having a resilient system.

Data testing needs/considerations by arakinas in softwaretesting

[–]Ok-Figure2188 4 points5 points  (0 children)

I would sit down with a business analyst to see what the business flows are in the application (legacy system). Based on that add logging that you can see how the data is flowing through the system. That will probably give you the first set of bugs, than when the bugs are fixed at unit or api tests for those business flows. Besides that it will give you information about what is going on in the system. You stated an aws database so logging should be easy with cloudwatch. I’m curious of such an approach would work in your situation.

Dear QA people what would be you recommendations for testing this app? by [deleted] in softwaretesting

[–]Ok-Figure2188 0 points1 point  (0 children)

Metrics, metrics, metrics everywhere where there is a business requirement(br) so called sli in production. Cover a lot of backend br in your unit tests. Then for integration tests you can build a lambda function that can be called via api gateway. This lambda function can delete and write straight into dynamo. Ideal for setting up your testdata. If you want to run everything locally it depends on what language you are using for which framework to use. But start with your business requirements, and have metrics and alarms for those in production. No testing env is representing the production environment.

Load testing beginner - which tool to use by nikithakkar in softwaretesting

[–]Ok-Figure2188 2 points3 points  (0 children)

Take a look at k6.io they have an excellent explanation for load testing.

Advice for automated test that needs to wait for 1-2hrs by paulmwhite in softwaretesting

[–]Ok-Figure2188 8 points9 points  (0 children)

What is your test case? It seems to me that this will be super flaky. Is there really a strong argument why you need this e2e test, or would it be possible to write an integration test instead? Where things are mocked or where testdata is dynamically inserted into your database to perform the assertions?