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:
文章來源于領測軟件測試網 http://www.kjueaiud.com/
