For the detailed information from Internet, you can refer to the following links, include chinese and english verison.

English version:

Regular-Expressions.info(http://www.regular-expressions.info/)

Regular Expression--Wikipedia(http://en.wikipedia.org/wiki/Regular_expression)

Regular Syntax Summary(http://www.greenend.org.uk/rjk/2002/06/regexp.html)

Introduction to Regular Expressions(http://msdn.microsoft.com/en-us/library/28hw3sce.aspx)

Chinese version:

正则表达式--Wikipedia(http://zh.wikipedia.org/w/index.php?title=%E6%AD%A3%E5%88%99%E8%A1%A8%E8%BE%BE%E5%BC%8F&variant=zh-cn)

正则表达式参考文档(http://www.regexlab.com/zh/regref.htm)

正则表达式三十分钟入门教程(http://unibetter.com/deerchao/zhengzhe-biaodashi-jiaocheng-se.htm)

When I want to run "db2sampl" to create a sample database, I found many db2fm processes via "top" command and the CPU usage rate was 100%.

The problem is caused by db2fm consuming a great deal of CPU resource, which leads to 

unexpectedly high CPU usage on the system.

I found out two approaches to solve it from http://www-1.ibm.com/support/docview.wss?uid=swg1IY64683 

and 
http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/core/r0008306.htm


1. Restart the system after comment out the the db2fmcd entry in /etc/inittab to prevent 
it from respawning automatically as below:
--------------------------------------
# end of /etc/inittab
#fmc:2345:respawn:/opt/IBM/db2/V8.1/bin/db2fmcd #DB2 Fault Monitor Coordinator
--------------------------------------

2. Install the DB2 V8.2 fixpak 3 later.
Here is the solution approach from internet, please refer to: db2fm usage rate was 100%

For more detailed-chinese information about Cron, please refer to Cron用法说明 and Cron Help Guide

1. Record/ Playback Testing Tools

Record the actions of manual test execution, allowing tests to run unattended, thereby greatly increasing productivity and eliminating manual testing mind-numbing repetition. However, even small changes to the application under test require manual re-recording of the test. This first generation of tools, therefore, is neither efficient nor scalable.

Pros	Cons
• No programming skill necessary! • Allows users to quickly generate automated tests based on existing manual test cases • Little or no training needed to start creating test automation	•  Often times the scripts recorded scripts don’t work correctly, so you must edit them manually (you end up programming!) •  Recorded scripts are very vulnerable to UI changes. •  Little or no reuse of scripts, which makes future updates difficult or impossible.

2. Scripting

Scripting, a form of programming in computer languages specifically developed for software test automation, solves many of the problems of capture/playback tools.

Script developers, however, must be highly technical, specialized programmers working in isolation from the actual testers. Additionally, scripts are best-suited for GUI testing and don’t lend themselves to embedded, batch, or other systems. And as changes to the application under test require complex changes to associated automation scripts, maintaining ever-larger script libraries becomes overwhelmingly challenging.

Pros	Cons
• Higher level of re-use, easier updates than record and playback. •  More maintainable and manageable (less code than recorded scripts). • In practice, you generally can record actions to generate code and then modify it to suit your needs. This technique saves time.	• Tests live in the code. To update a test, an automation engineer must update the code (high maintenance cost). • Testers have very little involvement in the creation of test automation in this approach. • This approach relies almost entirely on automation engineers.

3. Data Driven Testing

Separates automation scripts and data, decreasing testers’ reliance on automation engineers, and vastly increasing the possible variations and amount of test data. While greatly extending the usefulness of scripted test automation, data-driven testing remains maintenance-intensive.

Pros

Cons

• A parameterized test can be run many times with different input data. • Test data is now separated from the test scripts(lower maintenance cost) • Testers can update the data. • Automation engineers can update the scripts. • Test data can be created before the test have been completely developed, as long as you know the correct format for the data.

• Takes more planning and management than previous approaches. • Development of tests will usually take longer since mechanisms to access data must be created. • Tests still must be scripted by the automation engineer. Testers only have control over the data. • In this approach, tests are broken down into a series of actions representing the business processes of the SUT, such as enter client, transfer and check balance. • Individual actions are automated, not the tests. • The tests are now stored externally from the test scripts, typically in a spreadsheet.

4. Keyword Based Testing Automation

Keyword-based test automation’s elegant, structured approach simplifies work even further, reducing the time and expense of test design, automation, and execution by allowing team members to focus on their areas of individual expertise. Non-technical testers and business analysts can develop executable test automation from keywords representing recognizable end-user actions such as “login,” while automation engineers devote their energy to coding the low-level steps comprising those keyword actions, such as click, find text box A in window B , enter User Name etc.

Using this keyword-based method, test design are developed based on documents created by business analysts or marketing departments while the final details of the software to be tested are still unknown. This test automation process removes bottlenecks and facilitates effective use of highly-trained professionals’ expensive time.

The testing process further magnifies the keyword method’s cost benefits, as changes to the application under test typically necessitate revision of automation scripts. Using a keyword-based framework, changes to the application under test often require no new automation whatsoever or require merely simple alterations easily made by non-technical testers or business analysts, greatly reducing an organization’s maintenance needs. When necessary, automation engineers can make changes to the automated keywords without affecting the rest of the test.

Action-Based Testing, the foundation of TestArchitect, embodies the continued evolution of the keyword-based approach under the guidance of its original creator. Test design and automation organized around TestArchitect’s built-in actions and keywords often make possible automation of tests without scripting.

Pros

Cons

• Highest possible level of reusability and maintain abilities • Tests are separate from the automation, so testers can create and modify tests without having to change the underlying automation. • Testers can create the tests before the  application is ready for testing (just like manual test cases), based on requirements,  specifications, use cases, and other information. • One automation engineer can support many testers. • Testers can effectively create test automation without having to learn to write scripts in a test automation tool. • Automation test cases for the automation tool can also be used as manual test cases since they are easily readable and stored in a spreadsheet format that many testers are comfortable with.

• Setup time can be longer than other approaches. • May require a change in the way you approach testing and test automation.

5. Multi Level Keyword Test Automation

Multi-level keyword automation, a unique feature of TestArchitect, creates new higher-level actions from lower-level actions simply by typing names or dragging and dropping icons.

For example, the action Add Product To Inventory might be created by three simple, low-level actions: click, enter and click, to open a window by clicking on a button, copy text into a textbox in that window and click on a button to close the window.

Combining two or more high-level actions creates even more powerful actions, such as combining Add Product To Inventory and Check Product into one action called Update and Verify Inventory.

I will use the following software:

• Web Server: Apache 2.2
• Database Server: MySQL 5.0
• Mail Server: Postfix
• DNS Server: BIND9
• FTP Server: proftpd
• POP3/IMAP: I will use Maildir format and therefore install Courier-POP3/Courier-IMAP.
• Webalizer for web site statistics

In the end you should have a system that works reliably, and if you like you can install the free webhosting control panel ISPConfig (i.e., ISPConfig runs on it out of the box).

I want to say first that this is not the only way of setting up such a system. There are many ways of achieving this goal but this is the way I take. I do not issue any guarantee that this will work for you!

1 Requirements

---

To install such a system you will need the following:

• the Debian Etch Netinstall CD (the list of mirrors is available here: http://www.debian.org/CD/http-ftp/ - I downloaded this one: http://ftp.de.debian.org/debian-cd/4.0_r0/i386/iso-cd/debian-40r0-i386-netinst.iso)
• a fast internet connection.

2 Preliminary Note

---

In this tutorial I use the hostname server1.example.com with the IP address 192.168.0.100 and the gateway 192.168.0.1. These settings might differ for you, so you have to replace them where appropriate.

3 The Base System

---

Insert your Debian Etch Netinstall CD into your system and boot from it. Press ENTER to boot:

The installation starts, and first you have to choose your language:

Then select your location:




Choose a keyboard layout:

The installer checks the installation CD, your hardware, and configures the network with DHCP if there is a DHCP server in the network:




Enter the hostname. In this example, my system is called server1.example.com, so I enter server1:


Enter your domain name. In this example, this is example.com:


Now you have to partition your hard disk. For simplicity's sake I will create one big partition (with the mount point /) and a little swap partition so I select Guided - use entire disk (of course, the partitioning is totally up to you - if you like, you can create more than just one big partition, and you can also use LVM):


Select the disk that you want to partition:


Then select the partitioning scheme. As mentioned before, I select All files in one partition (recommended for new users) for simplicity's sake - it's up to your likings what you choose here:


When you're finished, select Finish partitioning and write changes to disk:


Select Yes when you're asked Write changes to disks?:


Afterwards, your new partitions are created and formatted:

• .NET基类库(包括 System, System.CodeDom, System.Collections, System.ComponentModel, System.Diagnostics, System.Drawing, System.Globalization, System.IO, System.Net, System.Reflection, System.Runtime, System.Security, System.Text, System.Threading等)

• ASP.NET (System.Web, System.Web.Extensions)

• Windows Forms (System.Windows.Forms)

• Windows Presentation Foundation (System.Windows)

• ADO.NET and XML (System.Data 和 System.Xml)

在Visual Studio 2008中启用参考源代码访问

在Visual Studio 2008中启动.Net Framework源代码访问可以参考Shawn Burke的博文：Configuring Visual Studio to Debug .Net Framework Source Code。

调试进入.NET框架库源代码

配置完成后，即可动态的加载.Net Framework的调试符号并调试进入到源代码中。调试过程中，Visual Studio 2008将会从MSDN源码服务器上按照需要下载符号和源码文件。

开发者的注释也包括在源文件中。在上面的例子中，你可以看到Control基类中的Dispose方法的注释例子。