I am doing agile testing in the Huawei process

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 Development:The Agile Manifesto is more valuable to individuals and interactions than to processes and tools; workSoftware is more valuable than a comprehensive document, customer collaboration is more valuable than contract negotiation, and timely response to change is more valuable than following a plan. Its core is: people-oriented, play a human initiative. third, traditional testing and Huawei Agile Testing Differentiate: 3.1, the traditional test1. Goalkeeper: Quality assurance to prevent unreliable, invalid, bug-filled releases. 2. Information providers: Provide a large number of positive information about the status of project development. Tell everyone which features are working properly, what functions are not working, and which bugs must be handled. 3.2. Huawei Agile TestingThe role boundaries of the test and development become blurred.　　Some people mainly do test work, some people mainly do development work, but in the process of rapid progress, everyone will be called up to test or support the work of testing. More responsibility: Help developers understand requirements and identify test specifications as early as possible. 3.3. The role that testers play in agile testing1. The test is the "headlights" of the project, which tells us where we are now and which direction we are going.　　2. Testing provides information to the project team, enabling the team to make the right decisions based on reliable information.　　3. The tester does not make a decision on the project release.　　4. The tester does not guarantee the quality, the whole project team is responsible for the quality. 5. Testing is not a bug-catching game, its purpose is not to dwell on mistakes, but to help find goals.... Iv. Design and review elements of Agile test Cases : 4.1. Design the test case based on the demand-use case scenario:1. The need-based use case scenario to design test cases is the most direct and effective method, because it directly covers the requirements, and the requirements are the root of the software, to verify that the requirements of the coverage is Software Testing's fundamental purpose. 2. Use the test case as a "live" document, because the requirements are "alive" and fickle.　　Therefore, in the design of test cases should be in line with the agile "timely response to change than follow the plan more valuable" principle. 3. The design of the test case is not a phase, and the design of the test case needs to be iterative, Software DevelopmentTo revisit and refine the test case at different stages. 4.2. Agile Test Case design principlesTypically, the design of the test cases we see is one of them. Test cases can be written very simply, or can be very complex to write. The simplest test case is the outline of the test, and only the content to be tested, such as the test design in exploratory testing, will only indicate which elements of the product need to be tested, the quality objectives to be met, the test methods that need to be used, and so on.　　The most complex test cases, like the work Order system interface in a bank teller system, specify the input of each data, the expected results and the method of inspection, the operation steps of the interface elements, the methods and tools of the specified test, and so on. The test case is too complex or too detailed to have two problems: one is efficiency and the other is maintenance cost.　　In addition, the test cases are designed too detailed, leaving the test staff to think less space, easy to limit the tester's thinking. If the test case is too simple to write, you may lose the meaning of the test case. The simplistic test case design does not actually "design", just the function module that needs to be tested RecordDown, it only works as a simple test plan in the testing process, alerting testers to what the main features of the test are.  The nature of the test case design should be to understand the requirements during the design process, examine the requirements, and document the test methods of the software system to guide future tests. Reprint: http://www.51testing.com/html/47/n-3650047.html

I am doing agile testing in the Huawei process