Defect tracking workflow is the life cycle of a defect. It describes the states of the defect from when it is created to when it is closed.
There are two main defect tracking workflow models: 1. Identify defect ONLY with “State”; 2. Identify defect with both “State” and “Resolution”. You can set up a defect tracking workflow system with either of them, but which one is best for you?
Let’s set up a defect tracking workflow with the most common defect states:
A lot of our clients ask us what is the best way to get QA and test involved in unit testing. Since this is a topic with which many development teams struggle we thought this question was interesting enough to be the topic of a webinar in our ongoing series on agile testing.
So please join us June 6 at 10 AM EST for our webinar on QA’s role in unit testing.
If you have question such as:
- Are you thinking to involve QA and test in Unit Testing but are unsure how?
- Or are you looking to improve you existing unit testing set up?
Join our webinar on: QA’s role in Unit Testing.
- Agile Testing
- Agile QA Team Dynamics
- Types of Testing
- Collaborative Unit Testing
- Unit Testing with distributed teams
Our speakers are two veterans of the field Mike Maheu and Jeade Kong. Both have extensive experience working in agile teams.
After our successful webinar on agile testing in March (http://www.youtube.com/watch?v=BVb2OB47P8I) we decided to delve deeper and are now holding a series of two webinars on agile testing in which we focus on test driven development.
Part 2 will be on Acceptance Test Driven Development and will be held Thursday June 27.
For agile testing, the more testers know, the better. With more relevant information and knowledge, agile testers can be sensitive to potential issues and therefore be able to provide more efficient feedback on an agile project.
Although implicit, most agile testers serve to bridge the product team’s expectation and actual development work. In this sense, agile testers play a critical role, especially when they possess valuable knowledge and skills to understand developers and product owners from different points of view. But to do this requires skills that are not common to many ‘traditional’ testers. What do these ‘agile testing’ skills include?
More and more companies are now using Agile as their development methodology. This requires that test cases be executed, completed in a short time, and repeated very often. To reach these objectives, automated testing is a must.
There are many ways to setup your automation testing system. The purpose of this blog is not to compare andconclude which one is the best; but mainly to show an example of creating and executing JSAS test automation, one of the automation platforms that we’ve been using lately. .
First, what’s “JSAS”? More
Testing Securities Exchange Systems is very complex and requires a significant amount of domain knowledge. Many of the domain-related rules are related boundary values and the change of some values evokes other changes as well. Here are a few examples of where we always ensure adequate test case coverage to handle these situations: More
I read an interesting statement from Marc Andreessen in an article from QZ . Andreessen says that soon there will be two kinds of jobs: jobs in which people tell computers what to do and jobs in which computers tell people what to do. While kind of agreeing with this statement I started to wonder where this would leave us, the people working in QA? More
One of the main concepts depicted in the Agile Manifesto is close communication among team members. However, in the real world, sometimes we have to face the situation that the whole agile team is split into several sub teams that may not be in the same location or time zone. This situation usually happens with global companies or when some work is outsourced to a services provider that may be in another country. As a specialized software testing company, we often have the situation where our customer develops their software while depending on us to be responsible for the quality assurance as a remote agile testing team.
With agile development methods now becoming more popular, we have had to adapt from a waterfall situation where we wait for a software build based on fixed time periods to a‘remote agile testing’model. To do this, we must have a very good plan. But even before starting the project, we think about a few soft factors that have a significant impact on success but are often forgotten. These include: More
Why do project managers often worry about the # of testers, and the ratio of developers to testers. It follows that how much functionality there is to test is determined by Why do project managers often worry about the ratio of the number of testers to developers? It follows that how much functionality there is to test is determined by the developers and what they produce but applying a simple ratio is simply not the answer. I’ve heard that the agile development paradigm requires more developers than testers. In my opinion, this is far from the truth. More developers may create even more concerns and increase the possibility of breaking the application if agile is not implemented correctly. So, what determines the number of testers needed? Over the years, we’ve developed a methodology to gauge the testing effort required based on several factors. More
Mobile applications are more and more composite applications. Data is gathered from many different sources and presented to the client. However most mobile application testing does not take into account all these different sources of information. But it is imperative to test your mobile service as the user will experience it. More