Tag Info

Hot answers tagged

9

As user246 says, tricks to force developers to test can always be gamed: you're much better off finding out why they don't like testing and what the actual problem is then building a culture of testing and quality from that. You're working in PHP - there are unit test frameworks available for PHP that your devs can use. If they have no idea how much trouble ...


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 ...


7

It depends, and there are no industry standards. Seriously. Any metric can be gamed (and will be, if you use it for assessment). I'm not aware of any standard approaches, not least because the teams are - or should be - evaluating themselves regularly and looking for ways to improve their own processes (if they aren't then they're probably using ...


7

First off, everything I say here should be checked against your job description - that's going to tell you what your employer expects of you. As a lead, you probably don't have hire/fire responsibility (that usually goes with the manager title), so your employer's expectations will probably fall into these areas: resource management - making sure that ...


6

OK...now that a few folks have voiced their perspectives on "boxes" let me try to answer your question. I am going to assume that we agree that by 'white box' testing you are referring to the act of designing static or dynamic tests based on the implementation of a programming language that performs some functional task or behavior in a software program; or ...


5

Since you seem to imply that you already know what data you are going to report on, why not have data populated real time and accessible via the intranet? At MS all test results are available to everyone on the project team via the intranet. Test data is usually consumed across the organization differently, especially in large organizations. So, people can ...


5

Good luck with that. Your developers are probably bright enough to subvert any gimmick or incentive you put in place. Instead, you need to face the problem head-on: testing needs to be a part of your organization's culture. That's not to say that every developer needs to love testing, or needs to prefer testing over development. Rather, developers need ...


5

There is no one "right" answer. The number and type of categories of defects that would be appropriate to your context depend upon several factors, including: Type of application Your team size The level and frequency of "in the hallways" conversations between people on the team The number of bugs you have "hanging around" waiting to be taken care of etc. ...


5

There's a few extra factors here that can impact the way you handle this problem: Do you get results for each test as it completes or do you have to wait until all tests complete? Do you have multiple machines on which to run the tests (and is it possible to do this) or are you tied to a single system running your tests in sequence? Can you break your ...


5

I'm going to start with my standard response: it depends. I'm assuming you're talking about computer games and not board or other kinds of games, but the computer game industry has something of a reputation for using a lot of unskilled testers. That reputation comes from the fact that the large game development companies can call on gamers who think it ...


5

I'd suggest you start with the software quality blogs and forums around the Internet. Some of the online portals I like are: Joe Strazzere's All Things Quality The Software Testing Club portal (they have a pretty good forum, too) The Ministry of Testing portal (their listing of tools is long and could use more detail, but has a lot of information condensed ...


5

Instead of an "either/or", it is better to think of test case or scenario testing as a tree structure: Trunk: This is common test set that are always run (e.g. launch the application) Branch: These are major scenarios that have few common tasks (e.g. "admin" vs "user" scenarios) Branch: ... (if needed) Branch: ... (if needed) Twig: Test cases that are ...


4

This problem hits everyone with a decent-sized application sooner or later. Some of the things you can do to help manage your test cases more cleanly: Use a self-documenting system - if you're coding Selenium with C#, use the MS XML commenting and something like Sandcastle to publish the documentation that's generated on build to a common site. That way ...


4

As you say - 'it depends' but a few comments from my experiences: If you supply exact steps and data then what is the point of UAT? You might as well get your testers to run the scripts. I'd rather give the users some training on the system and give them scenarios to follow - which will have been developed with their input. Should anyone be able to run the ...


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

It is hard to find very knowledgeable security experts in QA, mostly because it is extremely complex, and requires constant learning and keeping up on trends. There are a number of things that you would absolutely need to know in order to be considered a "security expert". The biggest challenge is that it's not OK to know some of these things, or to have ...


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 ? ...


3

Naming and separating out your reused parts (tests, keywords for maps). I call this "common" tests/maps. If you already have alot of tests automated then this will be more tedious, but pulling out your unique maps and naming them appropriately will identify the actual controls that are being duplicate tested. Test Naming conventions that follow the ...


3

There are several factors to consider when selecting test data. For example, if your 200TB of production data is essentially equivalent, then you could potentially calculate a statistical sample from the total equivalent population. If not you could group your 200TB of production data into smaller equivalent subsets and calculate sample sizes for each ...


3

Your first step is to host the app on as close to a production environment as possible to eliminate "noise" from your load/performance testing. In the case of a test server, you'd want to keep everything else off it, have any database hosted on a separate system if that's your likely production configuration, and then start exploring the application behavior ...


3

Here are pros and cons of running tests in a sequence. I understood you ask in a context of automation, not manual execution. Pros: Execution time can take shorter, because previous test sets prerequisites for the next one. Cons: Harder to run in parallel. If you have a sequence of tests that depends on each other, you cannot run them in parallel. You ...


3

This is a pretty common situation - and one I've dealt with myself. Based on your comments and the question itself, I can offer a few suggestions. Document your test dependencies - if you're going to be running tests that depend on the result of other tests, make sure you document them. Build in per-test checks - it's a lot more complex to check the ...


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 ...


2

I made this sample spreadsheet for a project named Gmail (download it here). Some comments: Test Case ID: use this value to link each bug with one or more Test Case IDs. Test Case Description: they may be independent from each other or something like Run Test Case ID 4 Click on "submit" The Status columns (the ones with the colours) are pretty ...


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, ...


2

Take a look at the Test Matrix Report. If this does not have the needed column, register on TestLink Mantis and create a feature request (with the maximum level of detail). Regards Francisco Mancardi TestLink Team Leader


2

One thing that is often overlooked is to make use of your coverage tool(s) for more than ensuring that every line of code gets tested - if you configure your tool to produce a separate named output file for each test/test sequence then you can quite easily scan these for lines/blocks that are being tested in more than one test. The other key point is - as ...


2

Don't ask them to test. Ask them for the information you need. Help them understand what information you need, and what makes it valuable for you. Tell them what decisions you and others need to make that would benefit from good information about the system. Tell them what kinds of information would help you and others make better decisions. Ask for that ...


2

In addition to what the other responses have said: It's a lot easier to get a position in automation or as a lead if you're already doing the work of one whether you have that position formally or not. It looks from what you've said that you have the experience to claim this in terms of what you've done if not in terms of "number of years experience" (my ...



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