|
Communication Is Everything: A Conversation with Shachar Schiff Shachar Schiff, founder and principal consultant at BadTesting, chats with TechWell community manager Owen Gotimer about the recent rebrand of BadTesting, the four archetypes he uses to help customers, and the universal importance of communication.
Continue the conversation with Shachar (@Shak) and Owen (@owen) on the TechWell Hub (http://hub.techwell.com/)!
|
|
|
Dealing with a Test Automation Bottleneck The test team uses the test automation system to execute thousands of test cases because … why not? The tests are running automatically, for free, so there is no incentive to improve test efficiency. Just run them all! But eventually, as more and more tests are added, the system becomes overloaded. Test runs are delayed and you get a bottleneck. Don't throw more money—or new systems—at the problem; do this instead.
|
|
|
Defining KPIs and Metrics... I'm currently building out a Test PMO for an insurance company. We have a long term, fixed-price contract with a vendor using a waterfall model. I'm currently working on KPIs and metrics which I will use to tell the testing story, which means both technical and business comsumers will need to find value in them. I'm conducting targeted interviews atm but am interested in hearing if any of you have had experience in this arena.
What kinds KPIs / metrics have you found valuable?
What kinds of chatring / mapping have you found to be confusing?
What considerations would you want to address?
Any additional comments?
|
|
|
The New Role of Test Assurance Officer and Test Coach Testing has changed a lot in the last ten years. Although some traditional techniques are still useful, many testing activities are being done by developers, users, and other nonprofessional testers. Consequently, the role of test manager has changed into more of a test assurance officer and coach. The way this new role is implemented can differ from situation to situation. Here’s how it can be useful.
|
|
|
Dealing with a Test Manager’s Most Annoying Problems A test manager has to perform in multiple dimensions, using a variety of professional and interpersonal skills daily. With all these career facets, there are lots of different areas that can pose a problem. Here are the most common (and most annoying) things a test manager typically hears on a regular basis, as well as some strategies for how to deal with them.
|
|
|
Embracing Tools and Technology in QA: An Interview with Melissa Tondi
Video
In this interview, Melissa Tondi, senior QA strategist at Rainforest, discusses the foundation you need in order to have a positive introduction for new tools and technologies. She explains why the team leader has to understand what motivates each individual and how to get them excited about their job. Melissa says team members also have to realize that if they are in any way involved in testing software, they are a technologist, so they have to embrace the tools and technology that will continuously improve and streamline repetitive tasks.
|
|
|
Providing Value as a Leader: More Than Just Being the Boss
Slideshow
Being a test manager is more than just being the boss. Sure, there is direction to set, issues to address, hiring, performance reviews, and status updates.
|
Jeff Abshoff
|
|
3 Steps to QA Success from a VP of Quality Assurance
Slideshow
Are you a leader with a quality problem? Every organization struggles with quality at some point in their product lifecycle. Knowing what to measure and how to build a culture of quality with specific and actionable methods is key.
|
Karen Holliday
|
|
6 Ways Testers Can Add Value (Other Than Functional Testing) Many testers spend their time doing functional testing and don't come out of this cocoon. But software testing is all about discovering quality-related information to assist stakeholders in making informed decisions, and there are multiple ways to discover information in addition to functional testing. Here are six actions that will help you add more value to your projects.
|
|
|
Which good books regarding general automation approach you recommend? I am asking you to please recommend good books to read about general testing of an application.
Suppose you work at company, and a new client asks for his new software.
You know many tools, Selenium, Protractor, SoapUI, RestAssured, API Testing.
But what is the process you take to start the testing of the client tool?
How do you choose where to start testing from?
Specific about Automation.
How do you choose which API calls to test? Which are in the regression test suite?
How do you know how much testing is enough?
Tests usually dont fail, how do you look for tests that actually fail?
I have knowledge on tools, and I can do as I'm told,
but I want to be more as a test automation lead, so I need to have more experience
than just following the lead.
|
|