agile testing quadrants

Agile basic knowledge----demand management based on story (III.) (3) Daily station meeting The purpose of the station will be three: (1) Known progress Progress is known only from the level of user stories and tasks, and there are only two states of task progress: complete or incomplete (percent complete). (2) A well-known scheme What work will you do before the next meeting? (3) Throwing problems What's blocking your progress? ("No problem

Story based Agile basic knowledge----story writing Why use story? Software industry for more than 40 years, demand analysis technology has been very mature, but the MRD-driven process is overwhelmed. Since MRD often takes up a lot of time, MRD reviews take up a lot of time, and after coding is done, the pressure is poured into QA, often on the schedule, or the experience is poor, or there are too many bugs, or the project is postponed. Using story,

Ext.: http://blog.csdn.net/kerryzhu/article/details/8812589Today, we also discuss such an old topic, do you feel the same? Because Mr. Dening, who was Google's China Test manager two years ago (at the end of 2010), wrote an article on "What is Agile Software Testing" (published on the INFOQ website [1]), which has already been discussed, "Agile software

Agile basic knowledge based on story----iterative initiation and iterative review In addition to the need to explain the accident, there are only two meetings that require all team members to participate, namely, "Iteration Initiation" and "Iteration review." (1) Iteration Initiation will Before the iteration begins, an iterative launch will be convened for the following two purposes: Clear iterative cycle, that is, on-line time; Identify the ite

1, Agile Test Quadrant-the division of labor in each quadrant? Who will do it specifically? When do you do it? 2, soap opera Test 3, exploratory testing 4, session-based testing 5, WATIR6, Fit Fitnesse8, to ility testing (reliability, interactivity, scalability) 9, agile

Agile basic knowledge----demand management based on story (I.) Demand management based on story (1) Using story mode to manage requirements, the large MRD is divided into a suitable granularity, and can be independently delivered story (usually each story can be completed within 1-5 days, including design, development, testing), the requirements are clear, easy to reach agreement, and can save a lot of re

model to maximize the efficiency of the team. Whether you rely on pruning redundant documentation or providing a democratic, unobstructed communication platform, you can help your team focus on limited effort.* Test-driven developmentis to have the developer design and write the unit test code before writing the functional code, based on the understanding of the requirements. Think about how to validate the functionality that will be implemented, and then consider the implementation of the feat

Wen/Zhu ShaominOnce, after the developer completes the code for the current sprint task, the testers, developers, and product managers come together to browse the product and go through it, and the product manager discovers the problem and thinks it needs to make a big change to the functionality. At this time the developer estimated that it would take two days to complete the code, but the testers opposed it, we had only 5 days to test time, plus this new function is more, the development code

more than randomly tapping the keyboard to find the problem; The test needs to really understand the required solution, participate in the methodology plan used to deliver the product, understand the risks involved in the delivery method, and identify these risks as early as possible to take appropriate remedial action. Testing also requires driving the project to a successful direction and helping everyone understand the appropriate level of success

Today, there is a discussion of such an old topic, does it feel like a cliché? Because Mr. Dening, who was Google's China Test manager two years ago (at the end of 2010), wrote an article on "What is an Agile software test" (Posted on the INFOQ website [1]), has already touched on this topic, "Agile software testing is more of an idea, not a process." In 2011, I

Transferred from ThoughtWorks Agile Software Development is a kind of new software development method which has been paid more and more attention since the 1990 's, and it is a kind of software development ability that can cope with the fast changing demand, it is applied to the software project more and more as a new development mode. Agile Software Testing re

? If a unit test is performed for specific code implementations, the unit test code that is written will be changed as required, and it needs to be changed frequently, does unit test code cost too much? ? Unit tests should emphasize the intention and interfaces of external users (systems) to write tests and perform so-called black box tests? In this way, the unit test code written will be relatively strong, better able to adapt to changes in demand? ? This article uses JUnit and mockito to wri

In recent years, a word is very popular in software projects-Agile. Large and small projects usually contain the keyword "agile". In fact, agile itself is an idea of optimization, which is the product of software engineering development to a certain stage. In the face of the changeable market, all want to respond quickly to the market or customer changes. But how

[This article is the fourth article of agile Testing Theory and Practice (Article 1, Article 2, Article 3, Article 4, Article 5, Article 6, Article 7 )] As mentioned aboveQuasi-agile TestingThe model is almost the same as what we call agile testing. But to understand the t

[This article is the sixth article of agile Testing Theory and Practice (Article 1, Article 2, Article 3, Article 4, Article 5, Article 6, Article 7 )] 2. Encoding phase: After the requirement design stage is completed, it is necessary to beginEncoding phaseAlthough the development and testing needs to be synchronized, but the function has not been completed an

Http://blog.sina.com.cn/s/blog_8f58d8050102v75h.html With the rapid expansion and popularization of agile development, the question of whether Agile software development requires test engineers is being mentioned by more and more people, and the industry has two different views. I think: with the further promotion of agile development, from the perspective of fut

Essentials of agile Testing Author: Zhang yuanli Http://blog.csdn.net/vincetest Two days ago, the company organized a sharing meeting on the agile development model. For testers, in order to promote the efficient operation of the entire model, the testing was also agile, the

[This is the fifth article in Agile testing theory and practice (article 1, article 2, article 3, article 4, article 5, article 6, article 7 )] In the previous article "using tools to achieve agile development", I have already talked about the current development situation of our company and I will not repeat it here. It is mainly about using devsuite of techex

First, development and testing of the continuity of trouble?Facing complexity (customer): constantly revising plans, increasing budgets, inferior product quality ... Face Complexity (Project team members): Often work late into the night, submitted products are not qualified ...ii. Agile Testing objectives in Agile Deve

I have heard of agile testing a long time ago. The current company is said to have been engaged in Agile development before, but I don't know why I didn't continue. Now, the testing department is independent of the R D department. At present, the testing work is arranged an