Appendix
Some of the Conclusions Reached by LAWST Participants [10]
附录
LAWST会议上得到的若干结论
During the last third of each day, we copied several statements made during the discussion onto whiteboards and voted on them. We didn’t attempt to reach consensus. The goal was to gauge the degree to which each statement matched the experience of several experienced testers. In some cases, some of us chose not to vote, either because we lacked the specific experience relevant to this vote, or because we considered the statement ill-framed. (I’ve skipped most of those statements.)
在会议每天日程的后三分之一，我们把在讨论中得到的一些论述抄写到写字版上并进行投票。我们并非想获得一致意见。这样做的目的，是想看看每条论述与这些经验丰富的测试工程师的经验符合的程度。在有些情况下，我们中的一些人并没有投票，可能是因为我们缺乏对要投票的论述的具体经验，也可能是因为我们认为该论述不够合理。(这里我已经省略了大多数论述。)
If you’re trying to educate an executive into costs and risks of automation, these vote tallies might be useful data for your discussions.
如果你正试图把自动化的成本和风险告诉给你的一位经理，那么以下这些投票结果或许是你们讨论的有用数据。
General principles
一般原则
1. These statements are not ultimate truths. In automation planning, as in so many other endeavors, you must keep in mind what problem are you trying to solve, and what context are you trying to solve it in. (Consensus)
这些论述并非终极真理。在规划自动化时，由于投入了这么多的努力，你必须时刻记住哪个问题是你试图要解决的，以及在何种环境下解决它。(一致同意)
2. GUI test automation is a significant software development effort that requires architecture, standards, and discipline. The general principles that apply to software design and implementation apply to automation design and implementation. (Consensus)
GUI级自动化测试是软件开发中的一项重大工作。它需要架构、标准和纪律。适用于软件设计和实现的一般原则同样适用于自动化设计和实现。(一致同意)
3. For efficiency and maintainability, we need first to develop an automation structure that is invariant across feature changes; we should develop GUI-based automation content only as features stabilize. (Consensus)
为了效率和可维护性，我们需要首先开发一个不随特性改变的自动化结构。我们应该开发像特性一样稳定的基于GUI的自动化。(一致同意)
4. Several of us had a sense of patterns of evolution of a company’s automation efforts over time:
文章来源于领测软件测试网 https://www.ltesting.net/
