| || |
new to QA
Hi all, this is my first post here. I've been searching the forums for some general answers and guidance, but didn't get the info I was looking for. I recently started as an software tester intern at a local company, which is rather small. Mostly, I did black box testing, ran and maintained Smoke tests and sub system tests. I should also mention that since the company was so small, I was the ONLY member of the QA team. Well, what I'm looking to know, is what else is there to QA? I know that there is TONS of other tasks and methods of testing, but I have not been introduced to any. Can anyone help me to understand the field, and point me in the right direction for other types of testing? Thanks in advance.
Re: new to QA
<font size="2" face="Verdana, Arial, Helvetica">This is somewhat part of my department training...the first question I ask the new members of my department is to define quality, testing and how they relate.
Originally posted by J_Lee: Can anyone help me to understand the field, and point me in the right direction for other types of testing?
There are many definitions for quality but the three that I use a lot are:
1. A person's perception - because if something meets or exceeds that customers expectation then they will consider it a quality piece of work.
2. Something that has a certain degree of excellence would have a level of quality to it.
3. A physical trait (i.e. that is a quality individual or rather that person is good at something)
I use the following definitions for testing:
1. Is a way to determine the presence of quality or to try to obtain quality. (i.e. determine how well something works.)
2. Is also a way to find out how much someone knowledge, ability or intelligence that someone has. (essentially your trying to determine whether an individual has a level of quality to them)
So as maybe you see between the definitions that there is a level quality in everything and we try to determine at what level of quality is in each product, service or person. For managers in our company, I like to use this example when explaining our quality assurance department. We have a marketing pamphlet going out to a few thousand people, we send it out without someone testing it there might be a bunch of spelling errors, poor grammar and the graphics might not look very good. So what should be done before that pamphlet goes out is to proof (i.e. test it) to make sure that we don't see any spelling errors, poor grammar or the graphics don't look blurry and that it meets the specs/requirements for release. I use this example to explain that to assure that quality is done throughout the company and not just in what we develop and testing can be done in every function of the company.
So to get back to your question, you can setup up processes to test everything from how the application functions, how it performs, how secure the application is to proofing a pamphlet to making sure the expectations on a project are met.
I would really recommending looking through each of the forums read the faq sections for the ones that have sections and you may want to look at the following sites.
<a href="http://www.softwareqatest.com/" target="_blank">
Here is one with a list of different types of tests, which you can search the forums for more details on these:
Hopefully this will be enough to get you started. [img]images/icons/smile.gif[/img] I apologize if I got too wordy (tend to do that every once in a while).