<ruby id="rxdll"></ruby><strike id="rxdll"></strike>

    <rp id="rxdll"></rp>
      <del id="rxdll"><meter id="rxdll"></meter></del>
      <pre id="rxdll"><font id="rxdll"></font></pre>
        <pre id="rxdll"></pre>
      <p id="rxdll"><thead id="rxdll"></thead></p><dl id="rxdll"><progress id="rxdll"><form id="rxdll"></form></progress></dl>

      <ol id="rxdll"><thead id="rxdll"><track id="rxdll"></track></thead></ol>
      <i id="rxdll"><dfn id="rxdll"></dfn></i>
      <font id="rxdll"><meter id="rxdll"></meter></font>

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

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

        Challenges in Testing Web Based Applications

        發布: 2011-3-15 13:29 | 作者: 不詳 | 來源: 領測軟件測試網采編 | 查看: 44次 | 進入軟件測試論壇討論

        領測軟件測試網

          Challenges in Testing Web Based Applications    軟件測試

          Challenges in Testing Web Based Applications

          In this tutorial you will learn about Challenges in Testing Web Based Applications Introduction, Why testing Web Applications is different? Factors effecting Testing of Web Applications, Why technology platforms affect testing? Challenges in Testing Web Based Web Applications, Summary.

          Sponsored Links

          Introduction:

          Web based Applications are increasingly becoming more feature rich, important and also the most popular means for developing commercial systems. Most companies opt for developing web based software wherever possible. This helps in catering to large number of end users. The deployment of the apps (once the infrastructure is in place) is fairly easy.

          The web based applications are powerful and have the ability to provide feature rich content to a wide audience spread across the globe at an economical cost.

          Hence it is a daunting task to test these applications and with more and more features testing these apps is becoming even more complex.

          In this article we will study the challenges faced when testing these applications

          Why testing Web Applications is different?

          Testing web applications is different because of many factors scenarios affecting the performance and user experience.

          Web applications can typically cater to a large and a diverse audience. Web Applications can also be exposed to wide range of security threats. Web applications may open up illegal points of entry to the databases and other systems holding sensitive information.

          To ensure that the web application works reliably and correctly under different situations these factors need to be accounted for and tested.

          Hence a lot of effort needs to put in for Test Planning and Test Design.

          Test Cases should be written covering the different scenarios not only of functional usage but also technical considerations such as Network speeds, Screen Resolution, etc.

          For example an application may work fine on Broad Band internet users but may perform miserably for users with dial up internet connections.

          Web Applications are known to give errors on slow networks, whereas they perform well on high speed connections.

          Web pages don’t render correctly for certain situations but work okay with others.

          Images may take longer to download for slower networks and the end user perception of the application may not be good.

          Factors effecting Testing of Web Applications:

          As mentioned above Web Applications can have a lot of variables affecting them such as:

          - Numerous Application Usage (Entry – Exit) Paths are possible

          Due to the design and nature of the web applications it is possible that different users follow different application usage paths.

          For example in an online banking application a user may directly go to “Bill Pay” page and other users may check account balances, view previous transactions and then “Pay the Bills”.

          Generally a large number of usage paths are possible and all are supposed to work well.

          All these Permutations and Combinations need to be tested thoroughly

          - People with varying backgrounds & technical skills may use the application

          Not all applications are self explanatory to all people. People have varying backgrounds and may find the application hard to use. For instance a Business Intelligence application with “Drill-Down-Reports” may work out for certain users but not for others.

          Although this affects the design of the applications, but these factors should be tested in usability testing of the applications

          - Intranet versus Internet based Applications

          Intranet based applications generally cater to a controlled audience. The developers and architects can make accurate assumptions about the people accessing the apps and the hardware/software/technical specifications of the client machines.

        延伸閱讀

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

        21/212>

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

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

        国产女主播精品_国产片婬乱18一级毛片视频_国产午夜激无码av毛片不卡_国产精品欧美久久久天天影院
          <ruby id="rxdll"></ruby><strike id="rxdll"></strike>

          <rp id="rxdll"></rp>
            <del id="rxdll"><meter id="rxdll"></meter></del>
            <pre id="rxdll"><font id="rxdll"></font></pre>
              <pre id="rxdll"></pre>
            <p id="rxdll"><thead id="rxdll"></thead></p><dl id="rxdll"><progress id="rxdll"><form id="rxdll"></form></progress></dl>

            <ol id="rxdll"><thead id="rxdll"><track id="rxdll"></track></thead></ol>
            <i id="rxdll"><dfn id="rxdll"></dfn></i>
            <font id="rxdll"><meter id="rxdll"></meter></font>

              <mark id="rxdll"><dfn id="rxdll"></dfn></mark>