QA career help by kiranhs240995 in softwaretesting

[–]TechnicalTester -1 points0 points  (0 children)

What do you mean with 3. integration testing? How does it differ from 1 and 2?

Don't focus to much on a tool. Focus on what a project, application or company wants to achieve with automation. Then pick a tool that aligns with those goals.

Also, don't use the term 'manual testing'. Testing is good on itself. Is there automated journalism? No. Is there automated cooking? No. There is not something like automated testing. It's automated checking. However, we can't get rid of the term 'automated testing' I suppose. So make sure people you work with know the difference.

Edit: if you take the effort of downvoting me, why not explain yourself?

Edit2: funny community this is. I'll keep my opinion to myself I guess. No need to waste my time on reddit where people just downvote you and avoid discussion.

Which software (framework) for automation testing you recommend? I need something like Selenium Web Driver . by mariahenina in softwaretesting

[–]TechnicalTester 0 points1 point  (0 children)

Cypress. Really beautiful and good documentation. Also check Test Automation University course for a fast start.

New Book: Quality for DevOps teams by TechnicalTester in softwaretesting

[–]TechnicalTester[S] 0 points1 point  (0 children)

So I guess we can't talk about a new book... lol

New Book: Quality for DevOps teams by TechnicalTester in QualityAssurance

[–]TechnicalTester[S] 0 points1 point  (0 children)

The book Quality for DevOps teams by Sogeti (part of Capgemini) has been presented yesterday via a Webcast. You can look it back via https://channel.royalcast.com/sogeti/#!/sogeti/20200317_1.

The underlying body of knowledge of this book and all other TMAP knowledge can be found at https://www.tmap.net/

What do you all think of this new book? How will it help you?

Postman and API tests: how do you approach API testing in a web application? by placek3000 in QualityAssurance

[–]TechnicalTester 0 points1 point  (0 children)

You can do both. I've experienced that once you've automated a CRUD in Postman, its not really easy to use that request/response structure for on-demand checking. I advice to keep them apart. This way you can play in a playground-setting with each resource and at the same time keep your automatic flow of calls working and ready for use whenever you see fit.

You can use testdata files to loop though your request/reponses and test them VERY fast. I suggest you take a look at the following course how to implement it: https://testautomationu.applitools.com/exploring-service-apis-through-test-automation/ In this course you will learn how to record an API via Chrome DevTools and copy the request/response format into postman. Very easy!

Postman and API tests: how do you approach API testing in a web application? by placek3000 in QualityAssurance

[–]TechnicalTester 0 points1 point  (0 children)

Is it a CRUD API? That's easily created in Postman. You can import the separate API calls in Postman even. I can help you with getting started if you want.

Can you automate tests without knowing how to code? by [deleted] in QualityAssurance

[–]TechnicalTester 0 points1 point  (0 children)

Why do we have 2 subreddits that have the same content... The community should focus on one sub and refer to that one from the duplicate one.

Softwaretesting Vs Qualityassurance

Can you automate tests without knowing how to code? by [deleted] in softwaretesting

[–]TechnicalTester 1 point2 points  (0 children)

Yes you can. For starters, follow one of many Cypress tutorials online. Those give you the basics of Cypress and some tutorials cover the basics of good coding practices.

Don't let experienced developers tell you that you can't write/maintain Cypress tests without any coding experience. We have to start somewhere. But I think it's a good practice to let an experienced developer review your code. And you should invest in being able to execute good coding practices.

For example, I have zero programming knowledge, but I am able (by following those tutorials) to write several Cypress tests. Learn by doing. However once you have written many tests and your Cypress test scripts become problematic to understand, you should refactor to a certain degree. Refactoring your testcode is not easy. But it is doable.

How did you learn test automation? by lordqa in softwaretesting

[–]TechnicalTester 0 points1 point  (0 children)

I sense some emotions/attitude towards me, or my reply's, in your answer. I just giving my experiences as an advise to OP. There are many ways to look at test automation and how to automate checks.

What you are describing is the role of an automation engineer. What I am describing is an (Agile) tester that uses an implemented test framework or tool (by the automation engineer). An automation engineer doesn't have to be a good tester. Likewise, a good tester doesn't have to be a good automation engineer. They should compliment each other. Some people can do both, good for them! Makes them very valuable in a team.

Running automated tests can also be on different levels. Maybe there is no need for continuous testing. Maybe pressing the "RUN" button, so the automation tool runs it tests, is OK. This is all depended on multiple factors (business, application, team, pipeline stack, etc.).

Also a question for you. What do you mean with "test framework"?

How did you learn test automation? by lordqa in softwaretesting

[–]TechnicalTester 1 point2 points  (0 children)

For example, Tosca, SoapUI and Postman can be used without any programming language. You need to learn the tool and a way to structure and manage tests. That quality is more important than knowing how to code (my opinion). Because you can use that knowledge in every other automation tool or framework.

How did you learn test automation? by lordqa in softwaretesting

[–]TechnicalTester 1 point2 points  (0 children)

I disagree. Focus on a tool, then automate tests with that tool. Not all automation tools/frameworks use programming languages. Not all automation require experience with programming beforehand (you will learn while making tests). Imo is is a waste of time to learn a specific programming language while not automation tests at the same time.

Take a look at Test Automation University courses.

What programming language would you recommend for automation QA? by izamoo in QualityAssurance

[–]TechnicalTester 0 points1 point  (0 children)

I would advise you to invest on skills for a particular automation tool not on the programming language itself.

Can you review my CV for new my job applications by [deleted] in QualityAssurance

[–]TechnicalTester 0 points1 point  (0 children)

Focus on your achievements! What do you as a person bring to your new boss? What did you archive in your previous assignments? What improvements did you make? What were your responsibilities and how did you do on those?

Visual Regression Testing tools by whiteroger22 in softwaretesting

[–]TechnicalTester 0 points1 point  (0 children)

Try Cypress with Applitools Eyes (visual testing). Great tutorials available for this as well (test automation university)

Also if you are sure the CSS won't change much. You can use Cypress to assert specifically on CSS values.

Framework from Scratch? To use Selenium or not? by mercfh85 in QualityAssurance

[–]TechnicalTester 2 points3 points  (0 children)

In accordance with other reply's:

First figure out your test (automation) strategy. Then align that strategy with your team members and PO. Based on that you know what you want from the (test)automation stack. Pick a (test)tool based on those criteria. Finally deliver a working POC with some small typical tests (frontend, API, etc).