• <ruby id="5koa6"></ruby>
    <ruby id="5koa6"><option id="5koa6"><thead id="5koa6"></thead></option></ruby>

    <progress id="5koa6"></progress>

  • <strong id="5koa6"></strong>
    • 軟件測試技術
    • 軟件測試博客
    • 軟件測試視頻
    • 開源軟件測試技術
    • 軟件測試論壇
    • 軟件測試沙龍
    • 軟件測試資料下載
    • 軟件測試雜志
    • 軟件測試人才招聘
      暫時沒有公告

    字號: | 推薦給好友 上一篇 | 下一篇

    改進自動化測試套件的可維護性(四)

    發布: 2010-6-22 10:47 | 作者: 不詳 | 來源: 領測測試網采編 | 查看: 10次 | 進入軟件測試論壇討論

    領測軟件測試網

      Even though we all agreed on this in principle, we had examples of disorganized or poorly thought out test matrices, etc. If you do a poor job of design, no one will be able to understand or maintain what you’ve done.

      雖然我們原則上都同意以上觀點,但是我們還是能舉出組織不好或思考不周的測試矩陣。如果你的設計工作做的不好,那么沒有人會理解并維護你做的東西。

      21. There can be multiple interfaces to enter data into a data file that drives data-driven testing. You might pick one, or you might provide different interfaces for testers with different needs and skill sets. (Consensus)

      有多個接口可以把數據輸入到數據文件中,以驅動數據驅動測試。你可以選擇一個,或者為不同需要和技術的測試者提供不同的接口。(一致同意)

      Framework-driven approach

      框架驅動方法

      For a while, the framework discussion turned into an extended discussion of the design of a procedural language, and of good implementation practices when using a procedural language. We grew tired of this, felt that other people had tackled this class of problem before, and we edited out most of this discussion from our agreements list. I’ve skipped most of the remaining points along these lines. Here are a few framework-specific suggestionss:

      在一段時間里,對框架的討論變成了討論設計過程語言以及良好實現過程語言的延伸。我們對此變得厭倦了,覺得已經有人在以前解決了這類問題,并且我們已經從我們的協議列表中刪去了這個議題。我省略了沿著這條思路下去的多數要點。以下是一些針對框架的建議:

      22. The degree to which you can develop a framework depends on the size / sophistication of your staff. (Consensus).

      是否開發框架取決于你的員工的數量和熟練程度。(一致同意)

      23. When you are creating a framework, be conscious of what level you are creating functions at. For example, you could think in terms of operating at one of three levels:

      當創建一個框架時,要注意你在哪個級別上創建函數。例如,你可以考慮下面三種級別之一:

      menu/command level, executing simple commands; 菜單/命令級,執行簡單命令

      object level, performing actions on specific things; 對象級,對具體事物實行操作

      task level, taking care of specific, commonly-repeated tasks. 任務級,負責具體的經常反復執行的任務

      You might find it productive to work primarily at one level, adding test cases for other levels only when you clearly need them.

      你會發現主要在一個級別上工作是高效的。所以,只有當你明確了需要在其它級別上添加測試用例后,才可以這么做。

      There are plenty of other ways to define and split levels. Analyze the task in whatever way is appropriate. The issue here is that you want to avoid randomly shifting from creating very simple tests to remarkably long, complex ones. (Consensus)

    文章來源于領測軟件測試網 http://www.kjueaiud.com/


    關于領測軟件測試網 | 領測軟件測試網合作伙伴 | 廣告服務 | 投稿指南 | 聯系我們 | 網站地圖 | 友情鏈接
    版權所有(C) 2003-2010 TestAge(領測軟件測試網)|領測國際科技(北京)有限公司|軟件測試工程師培訓網 All Rights Reserved
    北京市海淀區中關村南大街9號北京理工科技大廈1402室 京ICP備2023014753號-2
    技術支持和業務聯系:info@testage.com.cn 電話:010-51297073

    軟件測試 | 領測國際ISTQBISTQB官網TMMiTMMi認證國際軟件測試工程師認證領測軟件測試網

    老湿亚洲永久精品ww47香蕉图片_日韩欧美中文字幕北美法律_国产AV永久无码天堂影院_久久婷婷综合色丁香五月

  • <ruby id="5koa6"></ruby>
    <ruby id="5koa6"><option id="5koa6"><thead id="5koa6"></thead></option></ruby>

    <progress id="5koa6"></progress>

  • <strong id="5koa6"></strong>