We are the fifth team of software engineering method for the site-loving circle of QA and testing to take lessons Agile development requires daily summary of feedback every day there is progress every day.
A, QA
Early testing, frequent testing, provide timely feedback; asked the team responsible for the quality of software products, rather than an individual; work in multiple iterations; to conduct acceptance testing of the current task; and team members to achieve test automation; and also Panel members knot for the next iteration analysis, preparation of acceptance criteria and test cases. QA involved in the entire life cycle, play a role in each stage. Needs analysis, business scenarios and confirm acceptance testing; split test task, considering the estimated time and testing in the development of estimates on the basis of each story; and team members pair automated testing, and team communication problems found and defects; acceptance to provide quick feedback; but also to confirm the test and provide feedback; QA addition to independent test, usually need to keep different roles in pairs;
Our QA teams need to make their own proposals at every stage of participation; not only to verify that the design meets the requirements, but also to find out whether demand can truly reflect the purpose of analyzing whether there are inappropriate or missing requirements, identify risks, and risks associated with team communication; provide timely feedback on product quality to the team, easy to adjust; at the end of each iteration, when analyzing the defect statistics iteration, combined with knowledge of the test system quality, timely feedback with the team to discuss and analyze the reasons made as soon as possible improve, encourage team make persistent efforts. QA involved in every stage of the development process to help improve the quality of the team from the inside, so that quality into the product development in the past. Initiative to verify the quality objectives and timely to speak their minds, writing test plans, lists the activities to be performed and estimates, and the ability to test basic knowledge of testing tools, knowledge sharing within the team to help the team to participate in the test activities in the past, continue to provide and get feedback.
First, because our team using agile methods, we will need to do more of software testing.
He pointed out that the risk of software behavior may bring, and how to avoid these dangers and risks. Description of the conditions under no formal documentation of software testing, real-time test, test changes to the code, tested according to changing needs. Take the initiative to test as soon as possible, with the team working speed and efficiency consistent emphasis on integrity team. Team members sit together to talk; to participate in various meetings, continue to carry out software testing, and provide feedback. The entire team should be responsible for the quality, the whole team agreed on the quality of the entire team responsible for the quality of the product. Designed with the testability, test synchronization, write unit tests, using QQ bulletin boards plan to consider in detail the business processes, use cases, test before acceptance.
Development and testing teams are working. Each team member in addition to doing their own testing, but willing and able to do beyond the original scope of work, able and willing to help other members to solve other complex problems and achieve common goals of the team. Team personnel can proactively identify and make up an important part of the missing team, helping other team members to complete tasks. In time-critical situations, members of the group can be converted into other roles, give full play to the combat effectiveness of the individual, at the same time helping others, self-confident attitude and the skills to work in enhanced itself can achieve greater development. We have teams advance to ensure timely development tasks, critical tasks in the test, it can transform its functions to help test team to complete testing tasks. In addition, each member of the team, should seriously study and trying to find their own mode of agile teams and team members to communicate in order to reach a common understanding of agile development model, making the other team members fully understand their work and establish mutual trust among members.
When our group did not do unit testing or doing too little, then left a large number of quality defects during development time.
We first began to use test-driven development, list the needs, requirements to write a unit test script, write code so that previous tests can be when all the tests pass, you can start to write a test script, the demand for effective implementation All test scripts, start testing as soon as possible to begin system testing.
Learn Planned features to be implemented, the system design and functional test cases. First part of the test functions performed, and then gradually expand. Then began to use an iterative process to complete testing tasks, upcoming tasks into multiple test cycles, a key can be done to begin functional testing, you can do a complete safety testing, performance testing of reusable code with portions. Finally, we must learn to do the static test, do needs analysis, do the analysis of the design logic to understand the development, the need to read the code, the organization of work and individual. The strong ability to learn new colleagues into the highest technical content of an agile team, rich experience of colleagues into the code to do the underlying architecture of agile teams, so we have to in order to achieve the best combination of group and configuration.
Methods other than the conference, such as phone, instant messaging, e-mail to make up the difference of obstacles. In our profound experience, establish a smooth instant messaging, and information sharing database space is an indispensable factor in the success of the project. The often emotional exchange between team members, better able to promote mutual trust between the friction and lubrication to speed up communication between the teams.
In addition to encourage the team to self-management, self-construction, in the early stages to help distributed among the various regional teams set up some official communication it will be very helpful. Identify early stage can be a stable multi-party accepted regular meeting times and other effective communication, establish regular activity funds for various activities to promote the exchange of feelings between the organization team. In addition, to help team members based on the best team overall working time arrangements and changing individual normal working hours may also become one of the necessary choice.
Agile teams of managers, duty and responsibility to help each team to build the right amount of work plan, the team dynamic adjustment of tasks, in order to protect the overall steady progress. Focus on team work under pressure and to improve the rational allocation of team work plan, time in the long run, it has a very important role in improving the efficiency of work performance and team work of team members. Collaboration between the teams because each team has a more independent activity and decision-making, team members usually pay more attention to work within the responsibility belongs to the team, whether developers or testers subconscious will depend on the work of other teams developed and tested rearward into the development cycle, hopes all the necessary precondition and dependencies will ultimately be resolved, and then before you start this part of the work too late. Therefore, this project has become vulnerable teamwork progress can not guarantee the culprit.
In our project, also it had to do because there is no time between certain components of the interface definition of unified planning, resulting in the integration phase of testing and product development progress is very slow, the phenomenon of frequent problems, the team morale has been great harm. So as Agile teams should expose interfaces defects earlier, to design an appropriate amount of test cases covering the activities of this section, in addition to this part of the project management to solve the problem by means of external intervention, encourage team members to take the initiative to take on additional work is also co-ordinate inter team, the best way to reduce overall risk.