45 Habits of efficient programmers the way of practicing Agile Development study notes fifth Agile feedback

Guardian Angel

Recommended reading: The path to unit testing, JUnit Recipes, project automation

Use automated unit tests. Good unit testing can provide timely alerts for your code problems. If no unit tests are in place, do not make any design and code modifications.

Unit tests, like a small demo, are useful for learning reliable documentation of new APIs.

Use it first to implement it.

With TDD (test-driven development) as a design tool, it will bring you a simpler and more effective design.

The feeling is that coding begins only when there is a specific reason. You can focus on designing interfaces without being disturbed by the details of many implementations.

This form is really useless.

Different environments, there are different problems

Run unit tests in each of the supported platforms and environments using the continuous integration tool. Be proactive in looking for problems, not waiting for them to come to you.

Automated Acceptance Testing

Create tests for the core business logic. Have your customers verify these tests individually, so that they can be run automatically like a normal test.

The FIT (Integrated test framework) makes it easier to use HTML tables to define test cases and compare test result data with the data model of the customer-supplied Excel document, and we write tests to compare whether the price output of the application is consistent with Excel, thus automating the acceptance.

Measure the real progress

Measure the remaining work. Don't use inappropriate metrics to deceive yourself or your team, and evaluate the backlog to be completed.

We should not calculate the percentage of work done, but we should determine how much work remains to be done, and it is important to be honest here, to hide the truth without meaning.

Listen to the voice of the user

There is no stupid user, only a stupid, arrogant developer, behind every complaint hides a fact. Find out the truth and fix the real problem.

You will not be angry or dismissive of the complaints of your customers. You'll look at it and find out the real problem behind it,

Instead of saying to the client: This is not a bug, you just make a mistake that everyone will make.

45 Habits of efficient programmers the way of practicing Agile Development study notes fifth Agile feedback