I worked as a manual tester for 2 years and took a break because I had kids. Now when I apply for jobs, I couldn't get a call back as there is a gap in my career. It’s been 3 years since I worked and I live in UK.
I have taken selenium automation testing course online.And what are the recent technologies/tools that I have to learn so I can improve.
I am on a team of two working on standardizing testing for the company. The culture here is very resistant to change, as I am sure many colleagues on here have experienced themselves. I want to continue pushing this elephant up the stairs, but I am afraid some of these templates (IEEE 829 standard templates) are too dense for most of them. My mentality right now is to take this in strides. I want to avoid creating a 12 part test plan that people need to follow if they are just going to get defensive and say they do not have the time to even test, or test this way. Of course we have plans to educate as much as we can, but this is going to take years. What are your suggestions, then, with creating templates? Right now I have identified three that need to be used across all teams (Test Strategy, Test Plan, and Test Summary). We have plans on creating a best practice document/resource for teams to educate them on the industry standards.
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?
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?