Assuming you exclude the systems used to execute the application-under-test (Operating System, Browser, etc) there are no tools a tester cannot live without. There are many tools that make testing stronger, more thorough, easier, faster, and/or more efficient.
We use bug tracking tools, text reading/editing/printing tools, document storage and retrieval ...
Fiddler is a great tool for this kind of testing. It is an http proxy which allows you to send a request and then "fiddle" with both the request and the response between your app and going to the server. You can make small changes to a response, or create a response from scratch to send to your app.
Read MindMapping 101 from Darren McMillan - http://www.bettertesting.co.uk/content/?p=956
and this discussion ( prompted by myself ) on the STC - http://www.softwaretestingclub.com/forum/topics/im-the-map-im-the-map-im-the
They are nothing new, use of them seems to come in waves - as your question demonstrates :)
Disclaimer: We are the authors of Sahi, and this answers the original post and the next answer by Tarken. This is of course biased, but I hope in a sense of fairness this will not be removed :)
Hi Steve Miskiewicz, you should definitely check out Sahi. Don't be worried about the blogs and online presence. The problem space of web automation is small. You ...
Some additional tools to the others (+1 to Phil and Joe, great suggestions) mentioned:
Mind Mapping tool (e.g. XMind)
Database Querying/Scripting tool (e.g. SQL Server Management Studio)
Screenshot Capturing tool (e.g. PicPick, windows problem step recorder)
Data Generation tool (e.g. www.generatedata.com)
Browser specific dev tool bars (e.g. ...
Jing (Screens capturing tools)
Small little tool that let's you record a short video of the screen. I personally use this when taking screenshots or attempting to explain an issue becomes difficult. The next best thing is to record the problem. It also saves the clip on the cloud so you don't have to worry about finding a location to host the video.
There are many ways to expend the knowledge as a QA:
Read QA blogs.
Read Testing books.
Hone your QA skills by teaching others.
Go to Meet-Up & grow your network.
Search & Read the Research Papers.
Go to the Conference & Company Seminar.
One of the best ways to learn Ask Q/A on Stack Exchange sites.
Work on Open Source /Crowd Testing Projects. (...
Some ideas for the GPS part, based on my experience testing GPS's:
Do field tests, and choose you locations wisely- from totally open skies to crowded tall buildings with limited to no GPS reception, from standing still to driving slow and fast, change heights during the tests (GPS is less accurate in reporting heights), choose different times of day, ...
I'm not sure what kind of advice you are looking for.
You said "here's a lack of quick (not more than 8-10 hrs) and easily available tasks for staff evaluation. It would be nice to have 5-10 typical testing apps for checking various aspects of QA specialist skills".
Other than "Create them", I'm not sure what kind of advice we can offer?
I've created "...
There are several tools for the AI Driven Testing (AI-DT). here is the list of few tool they have some trial version period but not sure about the open source.
From my Experience I would Say Yes to VSTS Test Edition
I used VSTS Continiously ran load tests for 4 Hours, Simulated Maximum of 60 requests / sec with 4 Test machines, OLTP Application
Web Service / Biztalk / SQL Server / Replication / Service Broker based architecture
VSTS Tests - Easily bind data to tests. This is pretty straight forward ( http://blogs....
Actually, there's a bit of a distinction here - namely between whether something CAN be automated and whether it SHOULD be automated. Just about anything software does can be automated, but whether it should be is an entirely different matter.
For instance, if you're going to test whether a printout matches the on-screen display, the manual method is, more ...
This is a very good question... why ISN'T Sahi more common?
When I was evaluating tools a few years back I first tried Selenium RC and liked the overall nature of the tool but found, in my experience, in all honesty, it just didn't work. It didn't work well with IE (a deal-breaker for many) and was way too flakey (tests often failed for no reason, hung on ...
I'll try not to repeat any of the tools already listed. Some that I use extensively that I don't see in other answers are:
Fiddler - http debugging proxy
Beyond Compare - diffing tool for files or folders
Perfmon, Filemon, Processmon - monitoring different parts of the SUT.
Snipping Tool - screenshots
I think your suggestions are very good, it is always good to have clear guidelines. Though they should not be set in stone and should be used as a guideline and not as a rule.
In order to reproduce the issue I want as much information as possible. A screenshot can tell a thousand words. Some people make only a screenshot of the part they think ...
First of all, I doubt that there is currently something like AI-driven testing. *-driven means that your entire development/testing process strongly relies on *. Working for retest myself, I'm convinced—due to my experience there—that AI can be a great help to complement traditional testing approaches. But: Today's AI is inferior to hand-crafted test scripts ...
I like to keep things simple.
I work with a small team of testers and programmers. We like to keep things lightweight.
For managing charters and information flow, I use a spreadsheet and a whiteboard.
I categorize charters by product area. I haven't found getting more detailed than that to be useful to me (or others). I name charter files by their product ...
There's The Secret Ninja Cucumber Scrolls from Gojko - I started off with this
I'm currently reading The Cucumber Book from Matt Wynne
The RSpec book might also be useful
and a bunch of resources here
( I have no experience with ...
In the end I have gone with robotframework, as it is open source, well documented, and highly extensible. I've gone for the python version as opposed to jython, but this is mostly because I already have a decent python environment set up and have experience with python, but not java, so would like to be able to make use of its standard library in my test ...
I think it is because Sahi Open Source offers only a very limitied functionality compared to other free tools/api's like Selenium.
Sahi Pro costs USD 495! for functionality that you get from other tools for free like taking screenshots or grid.
Use whatever you are comfortable with. I'd suggest starting with something basic for recording notes like Notepad++. The important thing is to be able to keep detailed notes about your session, to setup a session charter, etc. Once you've got some practice with it, you can see what works and what doesn't.
I've used Rapid Reporter and Session Tester as ...
IMHO, a team lead who is a developer with less knowledge in testing, is the wrong kind of person to be selecting a test tool.
Do you have any QA Professionals on your team - perhaps someone with test tool experience? Or, lacking that do you have anyone on the team who will actually be tasked with using a test tool? I would suggest you turn to them.
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 ...
Yes, that would be awesome, but there is no such tool. (If you are very ambitious, you can try writing it yourself.)
The reality of cross-platform UI automation is that it is brittle and requires a lot of maintenance. Any vendor who claims otherwise is more interested in taking your money than solving your problems.
Here are some alternatives:
In this context, a goal you most likely want to achieve is one of Continuous Integration (CI).
To that end, from the developer side, every check-in will trigger a build (to perform certain checks and see if it passes). Then you will usually have a nightly build that gives you an up-to-date test environment every morning.
Now, this pipeline should include ...
1) As a free solution: You can use FFmpeg for full screen recording. For windows it requires ScreenCapturer (also free and opensource). For linux it can record the screen natively.
2) Camstudio is also a good solution. The output files may be huge, but you always can encode it with FFmpeg ...
I recently discovered PSR.exe, which is part of Windows 7 (just type in psr in the search field). It allows the user to record everything he or she does (like Snagit), but also makes it easy to add comments and to highlight certain regions of the screen. Once you finish recording, everything will be saved in a zip file as a so called ".mht" file. When you ...
When you compare SilkTest to Selenium and Watir, you are comparing apples to oranges.
If SilkTest were free and open source, you'd find tons of websites devoted to using it, and providing samples, tutorials, etc. But SilkTest is a commercial product.
If you search a bit, you will find places (like SQAForums.com's SilkTest forum at http://www.sqaforums.com/...
There are conventions that will facilitate faster testing. For example, if every translatable caption is fetched from a message catalog, you could merely check whether the message catalogs have been translated. (Different development environments use different terms for "message catalog", but hopefully the concept is clear.)
It is possible to tailor a UI ...