The normal:

 

Inpurt longer URL  e.g.  http://hosting.gmodules.com/ig/gadgets/file/110223881342456201530/jobsdb_lib_51.xml

The add button disappear hehe```

Introduction

Say goodbye to Microsoft Explorer's View Source, well almost. For those of us who do a lot of web development there has always been a need for a tool to examine the structure of documents we're working on; introducing Microsoft IE Developer Toolbar. The IE Developer Toolbar allows web developers to examine and change website's CSS, HTML, DOM, and Javascrīpt. Firefox web browser has enjoyed an excellent add-on, named Firebug, that provided this kind of functionality for some time now. This article, however, is not meant as a comparison between the two products. You may check Firebug if you're interested. Also, check out Firebug Lite for ways to integrate Firebug with Internet Explorer.

Installing IE Developer Toolbar

• Download the IE Developer Toolbar and run the installer.
• Close an re-open the Internet Explorer.
• Add the IE Developer Toolbar button to your toolbar
  
• Then close the window
  
• The IE Developer Toolbar button will appear in your toolbar for easy access.
  

Starting with the IE Developer Toolbar

Clicking the IE Developer Toolbar button you just added to your toolbar reveals the add-on. By default it is pinned to the bottom of the Internet Explorer window, but you may un-pin it by clicking the button located in the right upper corner of the tool. Note that whenever you pin or unpin the add-on the selected context is lost and you will need to re-select the element you were examining.

As you may see from the figure above IE Developer Toolbar comes with a number of options that enable you to examine your HTML document. To access it's functionality use the little toolbar and the menus.

Working With Documents

Perhaps the feature you may find yourself using the most is "Select Element by Click" available from the Find menu or the little toolbar button

What is particularly interesting about this view is that the exposed structure below is the actual HTML as defined in the source file PLUS any Javascrīpt generated DOM elements. Meaning, that by simply using View Source you don't actually see any HTML elements generated with, for example, document.createElement method, but in IE Developer Toolbar you do.

After clicking the "Select Element by Click" button the document's structure is shown in the tree view with the element you click-selected:

The above example comes from selecting the Search button of the Code Project home page. All of the selected item's pre-set attributes are shown along with their current values. Double-click a value in the grid to modify it. In addition, you may add attributes and their values to try them out. For example, with the above selection still active click the plus icon .
You should see the following:

Choose the background-color from the combo box, then type "orange" in the value column then hit the enter key. Notice that the search input box turns orange.

For ways, other than "Select Element by Click", to locate elements select Find >> Find Element... menu. The following dialog box appears:

As you may see you can search for elements using a variety of options.

Shortcuts

Right-click a node in the tree-view to get the following options:

These options allow you to view source of selected element with or without a style that it uses. This is a great improvement over having to search for an element's source code in the whole document hierarchy, Choosing Element Source, for example, produces the following for this selection:

Another interesting shortcut may be found in the Current Style list. Right click the style element you'd like to trace and choose the Trace Style context menu.

For this example the following shows up:

Clearly this makes locating the actual applied style quite simple. This may be particularly useful when dealing with multiple style-sheets and in-line style blocks that may override each other making it very difficult to determine which one is actually in effect.

Tools Menu

This tool may be of particular interest to UI designers. It features a resize option to preview screen at different browser resolutions, e.g. 800x600, 1024x768, etc. A more interesting features, however, are the Show Ruler and the Color Picker:

Show Ruler

This window allows you to draw rulers over any screen element to see it's dimensions.. You may click the black, red, or green box to show rulers of that color, or white to show none. For example:

Color Picker

you may avoid a great deal of mining through the code and style sheets before you find the color used. This tool makes it a snap.

Other Menus

Other menus are pretty self explanatory, use them to locate elements within the document or adjust Microsoft Explorer's behavīor.

• Disable - disables or enables scrīpts, pop-up blocker, and CSS
• View - enables you to quickly see element details on screen using labels. Especially check out the View >> Source options.
• Outline - similar to the View above, except it draws boxes around the elements it shows. Especially check the Outline >> Any Element... this option allows you to specify multiple search criteria for the elements you are trying to outline. Also, notice the Outlines >> Clear Outlines option, very handy when you specified a bunch of options.
• Images - similar to View and Outline but specifically deals with images. Check out the Images >> View Image Report.
• Cache - deals with the way the web browser processes cookies and the file cache.
• Validator - provide page validation using w3.org and other online tools. Checks for valid HTML, CSS, accessibility, etc.

Note

Some users reported problems with the Internet Explorer 7.0 following the IE Developer Toolbar reinstallation. Should you experience these problems, depending on your installation and a number of variables, you may find the following useful: IE Dev Toolbar 1.00.2188.0 annoying popup fix

Conclusion

While not a very mature tool, IE Developer Toolbar provides some useful functionality for examining and tweaking of web pages. Especially useful is the ability to locate elements through point and click. If you are a web developer dealing with the Internet Explorer, IE Developer Toolbar may make a great addition to your development toolbox.

推荐一款www.microsoft.com(微软官方)辅助测试的利器Windows下强大的任务管理器

Process Explorer 是一款增强型的任务管理器，你可以使用它方便地管理你的
程序进程，能强行关闭任何程序(包括系统级别的不允许随便终止的“顽固”进程)。除此之外，它还详尽地显示计算机信息：CPU、内存使用情况，DLL、句柄
信息.

 

Process Explorer v11.3

By Mark Russinovich

Introduction

Ever wondered which program has a particular file or directory open? Now you can find out. Process Explorer shows you information about which handles and DLLs processes have opened or loaded.

The Process Explorer display consists of two sub-windows. The top window always shows a list of the currently active processes, including the names of their owning accounts, whereas the information displayed in the bottom window depends on the mode that Process Explorer is in: if it is in handle mode you'll see the handles that the process selected in the top window has opened; if Process Explorer is in DLL mode you'll see the DLLs and memory-mapped files that the process has loaded. Process Explorer also has a powerful search capability that will quickly show you which processes have particular handles opened or DLLs loaded.

The unique capabilities of Process Explorer make it useful for tracking down DLL-version problems or handle leaks, and provide insight into the way Windows and applications work.

Download Process Explorer (1.6 MB)

 绿色汉化版下载地址:http://www.crsky.com/soft/1074.html

 

转自 卖烧烤的鱼博客 http://www.cnblogs.com/mayingbao/archive/2008/12/04/1347367.html

 转载必须经过本人同意并且注明

 

BUG ID- Summary
BUG ID:				Status:		New			Test State:	New Defects
Type:		F- Function		Severity		Severity 2			Priority:	High
Assigned to:				Reported By:					Reported On:	10/22/2008
URL/Area Path:
Subject:
Hardware Platform		Tested Platform		Browser					Test Environment
		Windows XP		IE7:					V6.test site
Bug  Summary
Steps To Reproduce:
Actual results:
Expected results:
Modified information					Retest  information
Developer:					Tester:
Modified Date:					Date:		10/22/2008

 

     搞怪測試 (Monkey Test) 一般見於軟體測試﹐測試者可以進行各種稀奇古怪的操作模式﹐用以測試軟體的穩定度。

     也有加以引用到其他產品之測試者﹐藉以測試產品設計之完整性﹐了解產品在各種使用模式的可能反應。經由搞怪測試所找出之失敗模式﹐吾人可以以進行分析﹐是否要變更設計﹐也有討論的空間。用白話來說，就是百般刁難，亂按一通，系統也不能當機掛點資料受損，這樣才稱得上經打耐操的好程式。
      Brian Marick在《软件测试的艺术》中说：复杂的测试会比简单的测试找到更多的bug。但是大部分的自动化测试都是简单的。我们期待一个输入后得到一个主要的输出，然后程序回到一个已知的基本状态，然后执行另外一个简单的测试。如果测试是深思熟虑的，则会找到好的bug。但是仍然是简单的测试。当我们回到程序的基本状态，则丢弃了前面测试的“历史”。而真正的用户不会这样操作，他们把一系列简单的动作串起来，形成一个复杂的环境。
 
    我们的简单测试不会模拟那些用户行为。因此如果一个简单的动作引起了另外一个动作的失败，我们的简单测试不会找到那个bug…但是我们的用户会找到它。但是使用聪明猴子，可以让我们的简单自动化测试变成复杂的用户场景。在测试中去掉“回到程序已知的基本状态”。然后让猴子决定运行哪个测试，用怎样的顺序执行。猴子会创建非常复杂的测试，并且持续测试你想要的时间长度。并且每次运行它都会创建不同系列的复杂测试。
 
    这种简单变复杂的测试的另外一个好处是我们可以确保程序在运行过程中正确地处理内存和资源分配。运行相同系列的测试，即使是复杂的测试，但是以相同的顺序和路径，即使一遍又一遍地运行也很少机会能发现内存和资源使用的bug。
 
     相反，我们需要使用复杂序列的、以前未使用过的测试。在这方面猴子比人更有效。
      我们将考虑两种类型的“猴子”：聪明猴子和笨猴子。聪明猴子拥有一定的知识，知道如何访问被测试产品的用户界面。它们在基本的功能层次上知道什么是可以做的，更重要的是，它们知道当进行这些操作时应该会出现什么情况。例如，他们可能知道选择“文件”菜单的“新建”项来创建一个新的文档，它们知道新建的文档会在新的窗口展示出来，窗口可以通过类名和文本来定位。如果没有出现新的窗口，或者窗口的标题或类名不对，“猴子”能识别出问题并报告一个BUG。

聪明猴子通常从一个状态表或者模型获取到关于产品的知识。通过随机地遍历这个状态模型，它们选择对于当前状态有效的选项，从一个状态转移到另外一个状态，然后验证到达了下一个期待的状态。如果模型包括错误处理状态的话，你还可以添加非法的输入到“猴子”的指令表。

by Barry Dorgan http://members.tripod.com/~bazman

Start Application by Double Clicking on its ICON

The Loading message should show the application name, version number, and a bigger pictorial representation of the icon.

No Login is necessary

The main window of the application should have the same caption
as the caption of the icon in Program Manager.

Closing the application should result in an "Are you Sure" message box

Attempt to start application Twice

This should not be allowed - you should be returned to main Window

Try to start the application twice as it is loading.

On each window, if the application is busy, then the hour glass should
be displayed. If there is no hour glass (e.g. alpha access enquiries)
then some enquiry in progress message should be displayed.

All screens should have a Help button, F1 should work doing the same.

For Each Window in the Application

If Window has a Minimize Button, click it.

               

Window Should return to an icon on the bottom of the screen

This icon should correspond to the Original Icon under Program Manager.

Double Click the Icon to return the Window to its original size.

The window caption for every application should have the name of the
application and the window name - especially the error messages.

These should be checked for spelling, English and clarity , especially
on the top of the screen. Check does the title of the window makes sense.

If the screen has an Control menu, then use all ungreyed options. (see below)

               

Check all text on window for Spelling/Tense and Grammar

Use TAB to move focus around the Window. Use SHIFT+TAB to
move focus backwards.

Tab order should be left to right, and Up to Down within a group box on the screen.

All controls should get focus - indicated by dotted box, or cursor.  Tabbing to an entry field with text in it should highlight the entire text in the field.

The text in the Micro Help line should change - Check for spelling, clarity
and non-updateable etc.

If a field is disabled (greyed) then it should not get focus.  It should not be possible to select them with either the mouse or by using TAB.  Try this for every greyed control.

Never updateable fields should be displayed with black text on a grey background with a black label.

All text should be left-justified, followed by a colon tight to it.

In a field that may or may not be updateable, the label text and contents changes from black to grey depending on the current status.

List boxes are always white background with black text whether they are disabled or not.  All others are grey.

In general, do not use goto screens, use gosub, i.e. if a button causes another screen to be displayed, the screen should not hide the first screen, with the exception of tab in 2.0

When returning return to the first screen cleanly i.e. no other screens/applications should appear.

In general, double-clicking is not essential.  In general, everything can be done using both the mouse and the keyboard.

All tab buttons should have a distinct letter.

Text Boxes

Move the Mouse Cursor over all Enterable Text Boxes.  Cursor should change from arrow to Insert Bar.  If it doesn't then the text in the box should be grey or non-updateable. Refer to previous page.

Enter text into Box

Try to overflow the text by typing to many characters - should be stopped  Check the field width with capitals W.

Enter invalid characters - Letters in amount fields, try strange characters like + , - * etc. in All fields.

SHIFT and Arrow should Select Characters.  Selection should also be possible with mouse.  Double Click should select all text in box.

Option (Radio Buttons)

Left and Right arrows should move 'ON' Selection.  So should Up and Down.. Select with mouse by clicking.

Check Boxes

Clicking with the mouse on the box, or on the text should SET/UNSET the box.  SPACE should do the same

Command Buttons

If Command Button leads to another Screen, and if the user can enter or change details on the other screen then the Text on the button should be followed by three dots.

All Buttons except for OK and Cancel should have a letter Access to them.  This is indicated by a letter underlined in the button text.  The button should be activated by pressing ALT+Letter.  Make sure there is no duplication.

Click each button once with the mouse - This should activate

Tab to each button - Press SPACE - This should activate

Tab to each button - Press RETURN - This should activate

The above are VERY IMPORTANT, and should be done for EVERY command Button.

Tab to another type of control (not a command button).  One button on the screen should be default (indicated by a thick black border).  Pressing Return in ANY no command button control should activate it.

If there is a Cancel Button on the screen , then pressing <Esc> should activate it.

If pressing the Command button results in uncorrectable data e.g. closing an action step, there should be a message phrased positively with Yes/No answers where Yes results in the completion of the action.

Drop Down List Boxes

Pressing the Arrow should give list of options.  This List may be scrollable.  You should not be able to type text in the box.

Pressing a letter should bring you to the first item in the list with that start with that letter.  Pressing ‘Ctrl - F4’ should open/drop down the list box.

Spacing should be compatible with the existing windows spacing (word etc.).  Items should be in alphabetical order with the exception of blank/none which is at the top or the bottom of the list box.

Drop down with the item selected should be display the list with the selected item on the top.

Make sure only one space appears, shouldn't have a blank line at the bottom.

Combo Boxes

Should allow text to be entered.  Clicking Arrow should allow user to choose from list

List Boxes

Should allow a single selection to be chosen, by clicking with the mouse, or using the Up and Down Arrow keys.

Pressing a letter should take you to the first item in the list starting with that letter.

If there is a 'View' or 'Open' button beside the list box then double clicking on a line in the List Box, should act in the same way as selecting and item in the list box, then clicking the command button.

Force the scroll bar to appear, make sure all the data can be seen in the box.

2. Screen Validation Checklist

Aesthetic Conditions:

1.        Is the general screen background the correct color?.

2.        Are the field prompts the correct color?

3.        Are the field backgrounds the correct color?

4.        In read-only mode, are the field prompts the correct color?

5.        In read-only mode, are the field backgrounds the correct color?

6.        Are all the screen prompts specified in the correct screen font?

7.        Is the text in all fields specified in the correct screen font?

8.        Are all the field prompts aligned perfectly on the screen?

9.        Are all the field edit boxes aligned perfectly on the screen?

10.    Are all groupboxes aligned correctly on the screen?

11.    Should the screen be resizable?

12.    Should the screen be minimisable?

13.    Are all the field prompts spelt correctly?

14.    Are all character or alpha-numeric fields left justified? This is the default unless otherwise specified.

15.    Are all numeric fields right justified? This is the default unless otherwise specified.

16.    Is all the microhelp text spelt correctly on this screen?

17.    Is all the error message text spelt correctly on this screen?

18.    Is all user input captured in UPPER case or lower case consistently?

19.    Where the database requires a value (other than null) then this should be defaulted into fields. The user must either enter an alternative valid value or leave the default value intact.

20.   Assure that all windows have a consistent look and feel.

21.   Assure that all dialog boxes have a consistent look and feel.

Validation Conditions:

1.        Does a failure of validation on every field cause a sensible user error message?

2.        Is the user required to fix entries which have failed validation tests?

3.        Have any fields got multiple validation rules and if so are all rules being applied?

4.        If the user enters an invalid value and clicks on the OK button (i.e. does not TAB off the field) is the invalid entry identified and highlighted correctly with an error message.?

5.        Is validation consistently applied at screen level unless specifically required at field level?

6.        For all numeric fields check whether negative numbers can and should be able to be entered.

7.        For all numeric fields check the minimum and maximum values and also some mid-range values allowable?

8.        For all character/alphanumeric fields check the field to ensure that there is a character limit specified and that this limit is exactly correct for the specified database size?

9.        Do all mandatory fields require user input?

10.    If any of the database columns don’t allow null values then the corresponding screen fields must be mandatory. (If any field which initially was mandatory has become optional then check whether null values are allowed in this field.)

Navigation Conditions:

1.        Can the screen be accessed correctly from the menu?

2.        Can the screen be accessed correctly from the toolbar?

3.        Can the screen be accessed correctly by double clicking on a list control on the previous screen?

4.        Can all screens accessible via buttons on this screen be accessed correctly?

5.        Can all screens accessible by double clicking on a list control be accessed correctly?

6.        Is the screen modal. i.e. Is the user prevented from accessing other functions when this screen is active and is this correct?

7.        Can a number of instances of this screen be opened at the same time and is this correct?

Usability Conditions:

1.        Are all the dropdowns on this screen sorted correctly? Alphabetic sorting is the default unless otherwise specified.

2.        Is all date entry required in the correct format?

3.        Have all pushbuttons on the screen been given appropriate Shortcut keys?

4.        Do the Shortcut keys work correctly?

5.        Have the menu options which apply to your screen got fast keys associated and should they have?

6.        Does the Tab Order specified on the screen go in sequence from Top Left to bottom right? This is the default unless otherwise specified.

7.        Are all read-only fields avoided in the TAB sequence?

8.        Are all disabled fields avoided in the TAB sequence?

9.        Can the cursor be placed in the microhelp text box by clicking on the text box with the mouse?

10.    Can the cursor be placed in read-only fields by clicking in the field with the mouse?

11.    Is the cursor positioned in the first input field or control when the screen is opened?

12.    Is there a default button specified on the screen?

13.    查看(479) 评论(0) 收藏 分享 管理

软件测试的艺术

Test Case Checklist

 

Quality Attributes

q  Accurate - tests what the descrīption says it will test.

q  Economical - has only the steps needed for its purpose

q  Repeatable, self standing - same results no matter who tests it.

q  Appropriate - for both immediate and future testers

q  Traceable - to a requirement

q  Self cleaning - returns the test environment to clean state

 

Structure and testability

q  Has a name and number

q  Has a stated purpose that includes what requirement is being tested

q  Has a descrīption of the method of testing

q  Specifies setup information - environment, data, prerequisite tests, security access

q  Has actions and expected results

q  States if any proofs, such as reports or screen grabs, need to be saved

q  Leaves the testing environment clean

q  Uses active case language

q  Does not exceed 15 steps

q  Matrix does not take longer than 20 minutes to test

q  Automated scrīpt is commented with purpose, inputs, expected results

q  Setup offers alternative to prerequisite tests, if possible

q  Is in correct business scenario order with other tests

 

Configuration management

q  Employs naming and numbering conventions

q  Saved in specified formats, file types

q  Is versioned to match software under test

q  Includes test objects needed by the case, such as databases

q  Stored as read

q  Stored with controlled access

q  Stored where network backup operates

q  Archived off-site

 

 

This checklist was part of a presentation at STARWEST 99 by Dianne Runnels, a project manager at Interim Technology

selenium tutorial 

Joyce原创，转载必须经过本人同意并且注明

根据公司需要和要求准备了这份selenium tutorial,希望对初学入门的朋友有帮助.

密码:留言或者加qq,1051926493 我会告诉大家 ^^