Good and Interesting question.
Here are some to make the tester's job easier:
Developers should perform basic testing before giving the product to the tester.
Include QA from the beginning of the project, not when the product is ready to test.
Work as a Team, not as two different departments [Developer & QA]
As the developer, never ask the QA to ...
Treat them as equals.
I have seen a lot of developers thinking they are more or better then testers in their companies and also treat them that way. Developers and testers have a similar goal: Making high quality software.
Quote:- If you can’t do great things, do small things in a great way.
Automated testing requires more discipline compared to manual, Learning automation is not difficult but it requires a focused and planned approach. Keep this in your mind Cheating is acceptable in automation if you understand what you are doing. As you have more than two months to finish ...
Just a few quick ones off the top of my head:
Run the code they've completed at least once on their machine before marking it as 'Done'.
Consult with QA on their intended route to implement a feature or bug fix to help flush out potential issues or bugs before even one line of code is written
Encourage QA to participate in sprint planning/grooming, design ...
I've worked in both roles for a while and my recommendation is:
Pair (before coding when possible) on test plans
See QA as an asset that is protecting you and customers from the mistakes we all make
Have an open mind when a QA approaches and avoid the (common) mistake of explaining away an issue as their lack of understanding
Don't assume that they can pass ...
You can always Google open source software projects and contact the developers and show interest in volunteering for Testing. You can also try below links and also get help from various Software Testing forums.
open testing Wikipedia mail list
Mozilla Wiki QA/Execution/Web Testing/Contribute
Oh boy! There is an interesting one.
Well apart from checking all the technical skills and blah blah, I always make sure to ask or observe two things about a candidate I am about to interview. And in my opinion someone who lacks this or are weaker in these skills, blows up his/her interview or rather, reduce their chances of getting hired.
As a tester, ...
This is a simple point, but very effective:
Be a developer who says "thanks" or "good catch!" or something positive whenever a tester finds a defect.
It's the daily currency of the respectful working relationship. All the formal processes are good, but they flow from the basic attitude of respect.
In addition to Michael Durrant's excellent answer :
Take time to make accurate bug reports. My rules of a thumb(I've been on both sides of the equation, which helps) :
Every hour spent in digging into the bug from the tester's point of view spares one day of work for the developer. Properly checking the exact conditions of the bug, the exact parameters, ...
To start off, have a positive attitude towards tester's activities & identified issues
Provide unit + dev-smoke tested builds to QA
Share release notes with info like included fixes, features and known bugs etc
Provide support in technical & back-end understanding of system
Provide support in analyzing hard-to-reproduce issues
Be appreciative ...
Why? In some ways the answer is quite simple:
Different testers have different backgrounds, experiences and motivations
To dig into this more however, here are the areas to address in light of that with the goal of improving things - probably the main goal of the OP asking this question and other readers of the question.
If folks do not ...
All the answers so far are good.
A few other comments:
Remember that the testers aren't there to make your life miserable. They're there to provide business stakeholders with information about how well the software fits what its intended users need from it.
Don't just throw code over the wall and figure the testers will catch any bugs. They might, but ...
What would be the possible responsibilities of being a Software Tester?
That is covered here.
I need to know if creating wire frames a part of Software Testing job?
That depends on what your employer needs and what you are capable of. In a tiny company, you might need to write the test cases, draw the wire frames, manage the bug tracking system, fix ...
The primary thing is to try really hard to find bugs. This may sound obvious but in fact often QA folks are intimidated by software developers and in addition many organizations reflect this in their workflow and processes. It is easy for a QA person to think, well if I PASS this and the developer can move on I will make them happy. While that might be ...
My opinion is communication. To communicate with developer, customer, business analyst and so on. Communicate with customer to get:
Better domain understanding ,Better acceptance tests, Better
And communicate with developers to get:
Better Test Automation code, Better Unit Tests
And communicate with business analyst to get:
With any application you are testing you need to learn the system. How is it used and how it generates revenue. Requirements come from that.
Who is using the system. What are the persona's and what is important for them. Understanding the users and their roles is key to see if something is a possible defect in their eyes.
Reporting defects should include ...
Even without a formal document, there are always requirements. You just have to work harder to find them.
You can talk to people and ask, then document what you heard. And there are some requirements ("must not crash", "must be consistent with a prior version of the application") that are usually implied.
Respect the time requirement for QA
All to often, test time becomes the project buffer time. If the release candidate is a day late, do you shift the release date or do you tell the QA folk to test faster or to test less?
Keep them it the loop if it looks as if there might be a delay.
Give the testers recognition (like bonuses, promotions, ...) if they ...
All good points here, but there's one I run into somewhat regularly as QA, that is to remember that while I may know the product fairly well, I do not know the code at all. It's generally frustrating being asked what part of the code has the problem. If I find a problem with a dog fetching a stick, I don't know if it's the dog class or the stick class. For ...
I read my Software testers' test cases and give them feedback. I ensure every workflow-path you only would know from reading the code is covered or at least brought to their attention. I also keep them up to date with features I myself that may not be really covered in meeting or UX specs (normally small fillers).
If the candidate already has some experience, I would say the following points:
When the candidate cannot show the added value of automation.
When the candidate cannot analyse which tests should be automated.
When the candidate is not able to find the root cause of a bug / is not able to isolated the bug.
When given enough time, the candidate cannot write a ...
Basically just about every live Open Source project welcomes everybody as a tester - the best ones to go for are those that you know something about the target use of the project. If you are a potential or actual member of their target audience your feedback will be much more to the point than if you are not.
List your interests to yourself in order of your ...
In general, IMHO QA supposed to be more focused on preventing
defects in the first place by fixing the process itself whereas
Tester is more concerned about finding defects as an after event.
A tester will take an requirement and validates the application by simply following it whereas a QA will question the requirement itself and will challenge the ...
There's reason to be optimistic. Quality assurance requires software development skills. Therefore, your skill set isn't separate from the role. What I suggest focusing on is how to supplement your current skill set for a QA position.
Skills to develop:
1) Testing best practices and methodologies (ie test driven development, test life cycle, agile ...
If your question is "Who is a tester" my answer will be "anyone who does tests".
But if you are asking who should be a tester, it will depend on the team resources, abilities and strategies.
When team members have different abilities, maybe the easier option is assigning someone the tester role and making him/her accountable for test assets.
On the other ...
Quality Assurance Engineer
Writes automation code, frequently for UI automation
Performs manual or automated testing. Can include free-style exploratory testing
Also, 'tester' often leads to second class citizen situations including significant pay differences.
To try and help level the playing field a little bit I use
I don't think this question relates to software testing per se but rather the motivation of the people in question.
There are lots of theories around the psychology in play in work situations - one that might apply in this case is Herzberg's motivation-hygiene theory.
Organisations now want to hire technical testers that can write automation frameworks in Selenium webdriver, Java/python and CI/CT tools etc.
Well, you already know how. It just takes time and action, you need to pick up one of these automation tools and learn it. That's your part and other ppl can only guide you on your way.
... don't let yourself ...
A lot of companies don't even do the difference between the two roles.
First difference, a QA has more responsabilities then a test analyst (I prefer this term than tester who is more seen as an executer of app ;) )
As a QA, you work to improve the process in general, it can be for software or for other process. You have the reponsability to measure the ...