Tag Info

Hot answers tagged

9

This is - sadly - rather more common than anyone here would like. It's where I was when I started at my current position: two major applications, both stable, but the company has never had dedicated test specialists before. The first thing I did was make sure that everyone knew there weren't going to be any quick changes. No matter how skilled a person is, ...


8

The traditional definitions would be something like this: A test suite is a collection of test cases related to the same test work. You might have a suite for regression, one for build verification tests, a suite that is specific for a component, and so on. A test plan is generally a document which describes testing approach and methodologies being used for ...


4

Webdriver is not only more modern. It is future W3C standard. Being able to click on hidden links seems like a misfeature. I would use old version only if newer version was seriously lacking important features without which I cannot live.


3

Since Selenium RC is deprecated and you touch on future-proofing, you should choose WebDriver. WebDriver expertise is more valuable to you because it's more transferrable. Yours is a future worth proofing. Over time, WebDriver expertise will only become more common than RC expertise. Subsequent hiring managers in your organization will appreciate this ...


3

In two words- Risk analysis. In a few more words- risk is usually defined as the probability of something going wrong multiplied by the damage caused by this something actually going wrong. Now you can use this definition to come up with more specific guidelines like- Is this feature stable ? Is this feature dependent on other less-stable features ? ...


2

If we refer to ISTQB glossary of terms then test suite: A set of several test cases for a component or system under test, where the post condition of one test is often used as the precondition for the next one. test plan: A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, ...


1

WebDriver is quite more reasonable option anyway. Everything you can automate with Selenium RC, you can do with Selenium WebDriver. If you can't perform some action with native methods (like yours "Being able to click on hidden links within sub-menus"), you can achieve the same with executing JavaScript commands from WebDriver. Selenium WebDriver will ...


1

Well, since this is an interview they are likely going to try and find out what type of questions you will ask. My response would be: I would first need to know what your developers are testing in order to be able to further test without just covering what has already been thoroughly tested. I would presume they are mainly focused on unit testing their ...


1

I think quite a few regular readers can relate to situation you described, and it is not easy to way out. :-) If documentation is not required by customer, and is used only for internal process (like if your customer is internal, and IT is just a cost center, or you are developing a website for a startup), people are tempted to develop as little ...


1

Anecdote: I worked on one project for a national company. Testing was being done and overseen by one of the Big Name consultancies. Their testers were told to take screenshots for every test step. They abandoned this practice as (1) it was taking too much time and test progress was too slow and (2) I was fnding 90%of the defects on the project by doing ...



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