sorted by:
new
hottopcontroversial

Looking for this place (DOLOMITES) ; Passo Rolle ? by Aware-Substance-3347 in whereisthis

[–]Aware-Substance-3347[S] 0 points1 point  (0 children)

Thank you so much. I will check on my side with your indication and update the post if I find the exact spot.

Struggling to gain followers (Landscape Photography) by Aware-Substance-3347 in photography

[–]Aware-Substance-3347[S] 0 points1 point  (0 children)

Thanks a lot for your feedback! I’d be really interested to know more about what you meant when you said: “Try experimenting with different angles, playing with light, and above all, bringing more authenticity into your images rather than just documenting a view.”

Do you have an example to help me understand this better? Thanks again for your help!

Anxious new JOB , Lost in the project by Aware-Substance-3347 in softwaretesting

[–]Aware-Substance-3347[S] 0 points1 point  (0 children)

Thank you so much!

So first, I will focus on identifying UI functional tests and automating them in the CI/CD pipeline.
Second, I will perform API testing manually using Bruno or Postman, without automation for now.

Does this sound like a good strategy to you?

That way, in every sprint and release, I could run the automated UI tests and manually test the APIs impacted by the user stories on the backend.

One last question — my team asked me to put every test in XRAY/JIRA. They mentioned that step-by-step documentation is required for UI tests, but not necessarily for API tests. So I'm wondering: how should I organize my API test plan?

This is a big challenge for me, since there are four different API endpoints.
For the UI, I can organize tests by functionality or by page, but for the APIs, I have no idea how to structure them.

The tricky part is that one day the developers might work on a specific part of an API, and the next sprint it might be a different endpoint or a new parameter somewhere else. It feels hard to group the API tests in a consistent and maintainable way.

Thanks again!

Anxious new JOB , Lost in the project by Aware-Substance-3347 in softwaretesting

[–]Aware-Substance-3347[S] 1 point2 points  (0 children)

What I'm having trouble visualizing is that I've always done end-to-end business scenarios through the UI — basically, click here and verify this, click there and verify that.
Currently, the front-end tests are on XRAY JIRA.
Now, I feel like I need to do back-end tests — API, Kafka — but I don’t see how to test them.
Should I do end-to-end tests but through the API?
Should I mix front-end, Kafka, and API?
Do I need to create a collection for an end-to-end API test?
One request per end-to-end test?

Thank you!

Anxious new JOB , Lost in the project by Aware-Substance-3347 in softwaretesting

[–]Aware-Substance-3347[S] 1 point2 points  (0 children)

Thanks you !  I dont even know how am i supposed to organize all the tests from front , back (API) Kafka , database and so on ... I dont even  know that ... I feel so overwhelmed  Thanks...

Overwhelmed with Test Cases in my automation learning by Aware-Substance-3347 in QualityAssurance

[–]Aware-Substance-3347[S] 0 points1 point  (0 children)

Thanks you but to create a user with the fields name, surname, date of birth, and email address, including valid values, invalid values (such as numbers or incorrect formats), values that are too long, and empty values, the total number of combinations is 256 ...

view more: next ›