Changes

* Gave up debuggingbookmark services API, continued working on framework.

==== Step 2. A Write a test suite holding variable called suite that holds all the your test cases. ====

If users want to change the menu item namefor a specific test case, they can open file '''unittesting.dtd ''' under folder '''local'''.

And then they can change the first item to your test case name in the file unittesting.dtd.

After adding the test cases to the extension, the participant can install the extension by drag and drop the extension into Firefox, and then click on install to install the unit testing framework with your test cases. You  Running test cases is also easy, user can click on '''Tools ''' menu from Firefox, and you will see an extension called '''Unit Testing for [...]'''. [[image:extension01.png|602px]] <br />  Select the '''Unit Testing for [...]''', system will pop up the following screen shottesting window.

[[image:extension01extension04.png|600px602px]] <br />

[[image:extension04Now click on the run button on test window, the test result will be displayed on test window.png|600px]] <br />

Users can also open the error console window to watch all testing logs. Here is the console window[[image:extension07.png|602px]] <br />

Now click on Further more, user can run test cases as many times as they want, and the run button result will be populated on test window. All logs will be displayed in consoleas well.

[[image:extension06extension08.png|601px602px]] <br /> {{clear}} === Unit testing log ===Right now, this framework provides a detail log for test running. This will allow users to track the detail testing process and any error that encountered during the testing. In order to check the error console, go to '''Tools''' menu in Firefox, and select '''Error Console'''. [[image:extension05.png|602px]] <br />

[[image:extension06-1After push the '''Run''' button, the testing process message will be displayed in console.png|600px]] <br />

Notice[[image: The framework runs the tearDown() when all the test cases are finished, which we can see the highlighting in the screen shotextension06.png|602px]] <br />

After pushing buttonNotice: The framework runs the setUp() first, which we can see the highlighting in the test result will be displayed on test windowscreen shot.

[[image:extension07extension06-1.png|601px602px]] <br />

Further more, user can run Notice: The framework runs the tearDown() when all the test cases as many times as they wantare finished, and which we can see the highlighting in the result will be populated on test window as wellscreen shot. [[image:extension06-2.png|602px]] <br />

* Instruction on how to write test cases by using this framework(readme.txt)

* Improve the structure of the framework and make it more easier for users if you could

Based on my experice in open source developing, I had a lot of fun for doing it. Also I'd like to address some improtant comments when we I was working on the open source.

* It was very time-consuming. Confidence and patience are the key to success. : This project has no prototype or even any example; most of time I couldn't get help because very less people work on this; and different people will do a different way in unit testing. It took me a lot of time to do researching, trying, and debugging. It also needs a lot of patience; if one way doesn't work, you still need to keep working on it until find the solution. You can take a short break and a deep breath, but never give up.* Documentation. : Any code we wrote should be documentated. It's very important for you to check back and for the people who want to contrubute to it.This is really important in open source community. Because I couldn't find the documentation for the Bookmarks services, I cannot make the bookmark unit testing work.* You need to get help from the others, but don't wait. : I had sent email to ask help for my problems, and I never get response. Especially It's kind of wasting time. You need to move on, especially in open source community, we do need help from the others, but don't relay on them.