Software Testing Concepts - As the name goes, the aim of this website is to explain various terminologies that are in use in the software testing domain. At the same time, it encourages experienced testers to provide valuable inputs to help others in need. It will also be a source of knowledge, tools, jobs, tips for interviews, etc.
So, jump in and start participating. My only request is - please be responsible and do not spam. The website is moderated and any account which indulge in activities that appear to be in violation of the spirit of this concept will be removed without notice.
Are you having trouble getting java to work with your firefox browser on Linux.
Unlike windows, where you install Java and lo it's setup with all the browsers seamlessly, on linux it appears to be different. It still requires some manual intervention to get this working.
We were trying to test an file upload applet for one of the products under test. The tests ran fine on Windows. But on Linux, despite reinstalling java and firefox, we couldn't get the applet to run.
I have come across a lot of people asking what should be the content of a test plan. So, for the benefit of our testing community, I'm attaching a test plan template that I created and being used quite effectively in our company.
This is by no means complete. Test plans can be tailored to be big or small. It all depends on the testing requirements of your organization and the complexity of the project.
Feel free to use and modify this to your requirement.
Here's the test plan template, free to download.
Bugs are inevitable in any software development life cycle. Everybody knows that. However, you have a deadline to meet. You have a release to get over with. There comes a point in time for a release when you take a call and decide what bugs to fix and what not to fix.
Here comes the importance of bug classification. The decision on what bugs to fix and what not to fix is made based on the bug classification.
Bug classification is done primarily to separate the most important bugs from the not so important ones.
Here's what one of the innovators in the open source industry says about a career in testing. I do agree with him.
Here's a very handy option to delete blank lines from a text file on Unix.
If it's a one time operation, you don't want to spend time writing a script for it.
Open the file using 'vi' editor [ # vi testfile.txt ]
Hit 'Esc' key to ensure you are in command mode.
Type :g/^$/d and hit Enter. You are done.
Here ^ means beginning of the line and $ means end of line (a blank line with no characters on it). 'd' means delete.
If there are space characters on the blank line, you could do this:
:g/^ *$/d
Evaluate what tests can best address the most important risks with the most coverage given the time, tools and resources.
Understand the Coverage:
Some of you may already be aware that 'Testlink' is open source test case management tool. If not, see my earlier post about Testlink here.
There are two great features provided with Testlink.
You've probably heard this term open source software many times before. Or you may be one of those geeks who has developed some open source applications. My intention of writing this is to help those testers who know little or nothing about open source software.If you are asking what is open source software? The following will give you an idea of open source software:
Today, I would like to share my thoughts as an interviewer (I'm leading a testing team and one of my responsibilities is hiring able candidates for the team). Here are a few points where some candidates disappointed me having projected themselves as prospective candidates.
My intention is to get a prospective tester to be sincere about himself/herself and a prospective interviewer to be cautious about candidates.