Front-end development tools necessary

1.firefox

      It is precisely because of the openness of firefox have a free tool less endless.

1.1   firebug

          firebug can view the page specified part of html, dynamic change, debugging javascript, change css, layout view. . . . A Swiss Army knife.     

1.2  web developer

          Can the standard of web pages, accessibility, and so do a lot of testing, you can easily disable css, javascript, view cookie, and so on.

1.3  html validator

            Details can be detected according to the DTD html html you do not meet the standards, and gives details of the solution path, the necessary strict mode

1.4 httpfox

           Often occur, the server accepts garbled, the head can not see the problem, but also very unlikely server log it, httpfox can fully accomplish the above tasks, view all communication of information between firefox and servers, such as response header, response content, request content and so on.

1.5 fiddler 

Online testing necessary, without having to build a complete test environment, js as long as you want to access mapped to the local js, convenient debugging, it fiddler

 

taobao ued recommended 25 plug-ins:

 2 .Internet Explorer

 While debugging is very inconvenient, but this is the only way the system practical.

2.1  Microsoft Script Debugger + Companion.JS

 Firebug is simply part of a simplified version of javascript. . . .

2.2  IE Developer Toolbar

         Corresponding to the web developper and firebug html, css functional part

2.3 httpwatcher

        httpfox enhanced version

2.4   fiddler

      Section with firefox, but it can be mapped to native code files online for easy local debugging.

 2.5 Internet Explorer Collection

          Because of the many versions ie, do web page must all be taken into account and can only be installed on a version of the general machine ie, Internet Explorer Collection can make us all installed versions ie to the unit (ie1 ~ ie8).

2.6 IETester (recommended Internet Explorer Collection )

  Because of the many versions ie, do web page must all be taken into account and the general machine can only install a version ie, while IETester can simulate all major versions ie (5.5 6 7), save a lot of open vmare resources: )

 Later, depending on the complexity test, IETester cookie problem exists, jsp can not read the information in the session.

3. later

       Being on so much, you can basically meet most of the testing and commissioning work,

Reproduced in: https: //www.cnblogs.com/JoannaQ/archive/2012/09/08/2676213.html

Guess you like

Origin blog.csdn.net/weixin_34233618/article/details/94153609