49

Well, apart from the obvious answer like "QA engineer should learn JavaScript to be able to use TA frameworks which work with JavaScript" I would say that a QA engineer should learn JS because knowing even basic aspects of how JS works or how it is applied to Web development brings you to a new level of defect hunting. Knowing basics of JS will let you: ...


30

It depends I've been in this situation more times than I care to remember, and the general process I use works this way: Triage all findings - At this stage I would be working to triage all bug findings into 4 classes: Blockers - any bug that makes it impossible for the product to perform the basic user acceptance tests, or breaks crucial functionality. ...


23

For hacking WebDriver without real production purpose, you need to find some task that really motivates you. Don’t forget, WebDriver – is not only about test automation, people use the tool (not so widely) for many different purposes: crawling some data from websites, semi-automating real job-related tasks. For instance, a girlfriend of friend of mine ...


23

It's not mandatory but It would be beneficial to know Manual testing before starting Test Automation. Test Automation is mostly used to reduce manual effort. Usually, in automation testing we don't actually test anything, most of the time goal is to automate manual tests. While in Manual Testing you will have to actually test the functionalities with ...


18

How you approach testing an API depends on a lot of things. Will the API be a public API that will be consumed by some external people/systems, or is it a part of a larger product's infrastructure? API is a general term that is sometimes used to describe anything from a COM interface, to a DLL or JAR you can reference, to a REST web service. Different ...


15

Quote:- If you can’t do great things, do small things in a great way. Automated testing requires more discipline compared to manual, Learning automation is not difficult but it requires a focused and planned approach. Keep this in your mind Cheating is acceptable in automation if you understand what you are doing. As you have more than two months to finish ...


14

To answer your questions: 1: What is the use of JavaScript for QA? UI Testing of web pages, when the UI is written using JS-based UI front-end frameworks like Angular and friends as is the current standard (there are many: Short and Brutal Lifecycle of JavaScript Frameworks) 2: If JavaScript is used for testing, what kind of things are tested using ...


13

One of the reasons would be to write end-to-end automated tests using Protractor. Protractor is an end-to-end test framework for Angular and AngularJS applications, where you write tests in javascript. It is designed to work better with angular applications better than pure Selenium. Additionally, knowledge of a programming language used in a project may be ...


12

You should never run automated tests against a website for which you don't have permission. The site owner could consider it a denial of service attack or an attempt at hacking. In theory, they could sue you or ask your ISP to drop you. If you do this using a company computer, you could put your company in jeopardy. Don't do it. Here are three sites ...


12

The most important skill, I think, is learning about the product. Learn, learn, learn everything you can about your product and how it is used. That tide will float about half of your boats. The other roughly half of your boats float on a different tide: your social skills. You need to do a lot of listening and offering support. Get to know the other people ...


12

As dzieciou commented, this can vary pretty dramatically. I will give you some ideas about what I look for when interviewing an experienced QA Engineer. One of the most important things I look for - whether the role is primarily manual or automated testing - is the ability to perform root cause analysis. For instance, if a candidate has experience ...


11

Yes, It is possible to find mentors outside of work place even for testing. Well maybe you wont have actual project as you do at the work place, but you can always come up with scenarios and work around them. Get your students to think and come up with scenarios or you define a few for them and then build up your training sessions accordingly. OR You can ...


11

The more you learn about the technologies your developers use, the better you will be at your job, and the more valuable you will be. In other words, even if you never write a line a JavaScript for your job, you will still be in a better position to test someone else’s JavaScript.


10

It depends, but I would like to argue that it is not that important. Test Automation Team: As a test automation engineer, you could get detailed testcase steps from someone else and just implement them. I see companies who do this as they have a seperate test automation team. In this situation understanding the tooling and how to build maintainable ...


9

A simple test strategy can only guarantee a simple assessment of quality. According to James Bach: The purpose of a test strategy is to clarify the major tasks and challenges of the test project. You can (and probably should) expand "tasks and challenges" to mean "goals, activities, deliverables, constraints, risks, and dependencies." Given that, your ...


8

'Welcome to the Internet' provides a ton of good real world examples that you can use to write some test automation code against. http://the-internet.herokuapp.com/


8

Kairu I wonder what has stimulated your question? Why do you think that you need mathematical skills? I'd say the most important things in no particular order are: Good broad IT understanding. A logical (but not specifically mathematical) mind. Experience of people using applications. Try to be an end user yourself and use as many different ...


7

If it's true that you "need to do some fairly thorough testing before we can sell this as a professional product.", have you considered hiring an experienced contractor? You could hire someone to come in and do the testing. Or you could hire someone to come in and do just enough training that your group of non-professional testers could get some testing ...


7

I am working under the assumption that you would be familiar with the language the tools are being written in. If the team you are on already is writing unit tests a good place to start might be with them. Talk to the developers that are writing the unit tests and get an idea for how the underlying code is working. In the process of doing this start ...


7

You're going to get a lot of "it depends" answers for this. Whether it's better to stay with primarily third-party automation will change depending on the quality of your third party automation providers, the nature of your business applications, your internal infrastructure, the method your third party people use and a whole lot more. Some of the factors ...


7

As a manual/exploratory tester who works very closely with developers I find that the best way to improve my effectiveness is to learn as much as possible about programming in general, plus the languages/technologies (e.g. Drupal, WordPress) being used. Being able to code to the same standard as a developer is not a requirement to be an effective tester, but ...


7

I highly recommend "Lessons Learned in Software Testing" by Bret Pettichord, Cem Kaner, and James Bach. In my opinion, this is the best book for an overview of software testing, without digging in too deeply. I have a review on my blog: http://www.allthingsquality.com/2011/12/book-lessons-learned-in-software.html When you have finished this one, you can ...


7

I consider that Selenium WebDriver has more value in Job Market as compared to Appium. Simply because requirements for web-automation are higher as compared to mobile-automation. This results in more jobs for WebDriver skills as compared to Appium. So you should have strong webdriver scripting, framework designing skills. Appium will be good as a side-kick. ...


7

First of all this is a managerial problem, not test per-se. Secondly there is no right answer here and it all depends on the context, maybe it's acceptable to release a lousy product, maybe it's safety critical product and you must stop it asap. Always start by communicating information, so collect as much information as you can into a easy to understand ...


6

A lot of this will depend on if you are getting a good return of investment from your third part testers and testing scripts. If the end result if a good regression suite with the ability to vary inputs and conditions at a reasonable price then there is less urgency to take the automation fully in house. Even if the third part testing scripts provide a good ...


6

Don't worry too much about the idea of testing a product which includes machine learning algorithms - you just need to make sure that it's returning accurate results. Primarily, testing ML functionality involves creating and uploading a training data-set (the developers may have one already), uploading a smaller more specific testing data-set, and then ...


6

I think the basic question should be "Why a software QA engineer should learn programming". Which programming language to learn is not important, it can always change. As a QA Engineer, you can work on projects from several platforms (web frontend, web backend, mobile, desktop, IoT devices etc). A QA Engineer could be required to: perform only manual ...


6

The simple answer would be that, If you see your self as a Manual tester, then you don't have to If you see your self as a Test engineer, then you have to Explanation: Manual testing: If you like playing around with the system, doing repetitive tasks, etc you don't have to learn automation testing. Automated Testing But If you see your self as 'Test ...


5

It is difficult to get direct feedback on testing skills, especially with regards to test techniques. I do have a couple of suggestions though: Find a testing mentor. This can be someone who has the same amount of experience you do but maybe in a different area or someone with vastly more experience. It doesn't really matter as long as you can learn from ...


5

Choosing the tool is not the only decision you need to make when testing an API. As for any testing task you need to decide: What aspects of the program are you testing? What application features do you want to cover with API testing? Are you going to verify some stateful scenarios (e.g. when user is logged in)? Or maybe you want to verify how an API ...


Only top voted, non community-wiki answers of a minimum length are eligible