| || |
- 1 Post By dlai
- 1 Post By dlai
Selenium or Mobile Testing...which is a good option?
I have 7 years of experience in Testing with knowledge of QTP. Now i wanted to come out of manual Testing..... So wanted to know which is a good option in USA Market....Selenium or Mobile Testing in terms of Pay Rates, Job Opportunities ...etc. And how much time is required to learn?
You can use Selenium on mobile testing.
Way too many variables to say how long is required to learn. Do you have a programming background? Familiar with object oriented programming? Understand xpath/css? There are numerous tutorials out there including free ones on youtube.
Originally Posted by m_sharus
Those 2 items I see are just subpoints on a skills section of a resume.
let's ask a higher level question... Do you want to be a Test Architect or a Test Manager, then drive your decisions from there.
I understand your point......i would also appreciate if you can give me some idea ...that what should be my next step to be an test manager.
For test manager, There are essentially 3 main things you need to know.
Originally Posted by m_sharus
1) Managing people
2) Managing Technical Risk
3) Managing project time lines on the testing end.
1. is pretty hard to simply take classes and show on your resume. You'll need to take on projects at your current work and step up to hard challenges and create a narrative/story of how that project used your leadership.
2. Technical risk you can get on a resume easily. It's a matter of spending a few weeks on each little thing. I'd probably start with the ideal company you want to work with. Then get familiar with the tools and frameworks they use, both on the testing side and on the dev side. For example, if you're looking at an angular shop, you'll want to learn some basic angular and learn protractor (a selenium add-on used in testing protractor apps) in detail.
3. Similar to number one. But you'll want to learn the implications of software process and the tools. For example, bug tracking, test management, requirement management, agile process (choose a flavor), understanding how to prioritize which activities, and how to accurately communicate with stake holders.
Last edited by dlai; 11-16-2015 at 08:59 AM.
Reason: spelling corrections
Some of the responsibilities if Test Manager
Understand the testing strategies by analyzing the requirements of clients to reach the expectations of the project.
Estimating time, resources, budget required to perform the testing.
Plan the Strategy
Build a testing team of professionals with good technical skills.
Identify the requirements and suggest it to the Project Manager
Develop the test plan for the tasks, team members required to mitigate the risks to system quality.
Arrange the Hardware and software that are necessary for the Test Setup.
Assign task to all Testing Team members and ensure that all of them have sufficient work in the project.
I have a similar question as I want to move into Selenium and come out of manual Testing - am 7 years experienced.
What would be the responsibilities/attributes of a Test Architect.
I am not interested in Managerial Domain.
Test architect has many of the same parallels as a normal software architect. But there are some key differences.
Software architects worry more about performance and scalability, trying to squeeze as much out of the hardware as possible. While a tech architect will favor reliability, as flaky tests creates a lack of confidence in the whole system.
Both are concerned about maintainability of the code base. A normally software architect looks at it from the perspective of using established software patterns that other engineers can recognize and maintain. A test architect is more concerned about maintaining the correctness of the test framework and tests. For example, a test architect may separate his/her project into separate repos based on business function (admin, user, premium features, etc..), while a software architect may do layers based on systems their code are being deployed to (data access, services, apis, web ui, etc...).
Both are concerned about breaking down projects into smaller pieces that can be accomplished by small teams. However, generally testing resources are distributed between several team while engineering resources tend to have dedicated teams (ex: backend, frontend, UI, API, security, etc...). So generally tech architects need the ability to manage cross functional teams with non-dedicated resources. This tend to cause the need for higher attention to details on specifications, entry and exit criteria, and a clear roadmap. As most testing infrastructure are done by different team members in an uncoordinated way.
Originally Posted by dlai