quality assurance Questions

I am asking you to please recommend good books to read about general testing of an application.

 

Suppose you work at company, and a new client asks for his new software. 

You know many tools, Selenium, Protractor, SoapUI, RestAssured, API Testing.

 

But what is the process you take to start the testing of the client tool?

How do you choose where to start testing from? 

 

Specific about Automation. 

How do you choose which API calls to test? Which are in the regression test suite?

How do you know how much testing is enough? 

Tests usually dont fail, how do you look for tests that actually fail? 

 

I have knowledge on tools, and I can do as I'm told, 

but I want to be more as a test automation lead, so I need to have more experience

than just following the lead.

 

Suppose you work at a Company. 

And a new Client arrives, he needs the system he has, and he continues to build, to be tested. 

What is the approach you take, to find

-which tests to approach

-which tests to automate

-which tools to use

-how to build a solution for that client Testing and Automation testing needs?

I have been in software test for medical devices/software for the last five years, across three different companies. With my prior two organizations we formally validated our web-based software products only for the one or two most recent versions of Internet Explorer (at those times). Having our software work in Chrome or Firefox were nice-to-haves, but we did not communicate to our customers that we supported those browsers,  I'm soon to start work on a major release of an existing product, and the Project has decided to officially test/validate only Chrome, based on our current knowledge that the current release has known issues with IE. Seems to me we could be taking the easy way out, and not taking into consideration what our users use (often by policy). Apparently we don't currently have that information, though, I have brought it up that we should try to figure that out. 

Historically, hospitals/labs/medical offices/etc have - by policy - typically only employed IE for business use, but I know market share in this sector has been shifting to Chrome. But how much/fast? General browser usage, and even entrprise usage statistics are easy to come by, but I'm banging my head at this point trying to find information specific to healthcare/medical research. 

What are your experiences/thoughts on this?

 

 

Everyone is now looking for the automation testing. Because there is lot of problem happening in manual test case generation and execution. So, how can I increase users for manual testing? is any latest features there? if it means, please let me know..

Currently, we have created a reservation system using outlook rooms. Each test environment within the lab has a "room" that someone can book in outlook and gives the user/tester the ability to see what labs are available. However, there are limits to the amount of information that can be supplied for each "room" and it really is not easy to see further details of the "room" (server image, server os, sql server version, application versions, etc). 

 

I know about LabAgenda, and may pursue this. But is there any other systems out there that people prefere? 

Which are the best test automation system for stress testing hardware and software algorithms?  

Right now we are getting lot of requirements from the client to verify the website has ADA compliance?

Can anyone suggest how to carry out this compliance testing?

If a Scrum "increment" is to be "done" by the end of the "sprint", where "done" means usable/releaseable, I assume testing has to be part of the sprint. Since sprints are not supposed to last more than a month, depending on the scope of the sprint goals, testing is either ongoing or occurs just before the end of the sprint. It seems on-going has to be the answer, but regressive testing of the new increment with previous incrments can grow into an increasing work item.

Does anyone with experience in this have thoughts to share so I can understand better how this is done?

So, I'm writing automation tests for a huge web platform. We have page objects folder with files for each web page which contain a great amount of selectors used in tests. Also, tests pertaining to one of the component/functionality are all grouped in one file. 

 

The main question is whether the functions used by multiple tests (and some will have assertions in them) should be written:

1. Functions w/o assertions in page object and those w/ assertions in helper file for that component/functionality

2. All functions in helper file

3. Functions w/o assertions in page object and write the rest of the commands with assertions in the specific tests even though they may repeat and make the file with tests huge.

Testing is done in javasctipt(more recent: typescript), selenium webdriver, protractor, jasmine.

I really hope someone can solve this conundrum since nobody in my office has enough experience to help me. Thank you!

p.s. Should we group tests in one file? or write wvery test in a separate one?  

 

It's a survey on usual test automation tools ( open-source vs commercial) and what people think (and want from) about them.

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.