Nose-Subunit

This nose plugin changes the default output to subunit format. This can be used along with buildbot to have better reports.

Installation

nose-subunit apparently depends on both nosetests and subunit.

The following command would install nose-subunit and all its dependencies:

    easy_install nose-subunit

nose-subunit can be also be downloaded manually from pypi or github

Usage

Enable this plugin with --with-subunit. This plugin is known to work with following builtin nose plugins:

• skip plugin
• multiprocess plugin
• failuredetail plugin
• stopOnFailure builtin feature (enabled by -x/--stop)
• testid plugin

The following plugins are known to conflict with subunit plugin:

• collectonly plugin: If you are only collecting tests, you probably don’t care about the output

Nose plugins not mentioned here are not tested by the author. Please feel free to report your experience about using nose-subunit with other nose plugins.

Source Repository and UnitTest

http://github.com/liucougar/nose-subunit

under the root of nose-subunit, run:

    nosetests --exe

WP BianHuan is a WordPress plugin for modifying the rendered HTML on the fly. It parses the post in a DOM and walk through it. In the meantime it provides its own plugin system for others to easily write XML/XHTML transforming magics. Now BianHuan includes these built-in features:

• Unlimited Link Indication: You can setup different CSS class for each kind of Links in your post, so an icon can be displayed besides it to represent what nature the link is, be it external http or email or ftp. You can even configure your owns, such as external links to Wikipedia. (Yes, the icons besides links in this page is added by this plugin). It can also add target="_blank" automatically if no target attribute was set for external links. (Replacement of Link Indication)
• Convert words into links: this is implemented in a plugin for BianHuan, and this feature is fully customizable. What’s more, as BianHuan uses DOM tree walking, it is smart enough not to convert a link already in a link or in a PRE tag or in some attributes. (This feature can replace the SH-Autolink plugin)
• This project based on WordPress AutoLink plugin by Rudd-o, so it does another magic: "it lets you insert hyperlinks, content and images in your posts and pages with easy-to-type shortcut URLs, which don’t become invalid when you change your WordPress content directory or the permalink structure of your site". In addition, it converts these kind of links automatically if you do not use the simplified format, and save them in database.

Compared to the original WordPress AutoLink plugin, BianHuan runs on PHP >= 4.4.0, and it does not require any special php extensions to work. It is based on ezxml library from eZ System.

Another improvement is that BianHuan makes use of WordPress filters/actions system to handle events and provides other plugins hooks to add more functionalities.

Hope you enjoy it: please grab it here.

Why should I choose it?

If you like me, searching for a plugin to do all the transformations like link indication/auto link/save the link in a safe way, definitely leads you to frustration: no such extensible while power plugin exists for WordPress 2.0. WordPress AutoLink plugin is close enough, however it only runs on PHP > 5 and does not provide a easy interface for plugins. Thus I decided to start this project.

In short, if you want a plugin to incorporate all these stuffs, then BianHuan is for you

Installation

Installation is simple and standard, just uncompress the zip file under your wp-content/plugins dir, and go to your Admin interface to activate this plugin. By default, after activation, the plugin still does not function, you have to explicitly tell it to do so by going to its options page and check the first box in that page.

There are bunch other options you may want to customize. This plugin is used here, and you can see source files to get some inspiration.

FeedBack

Please leave your feedback or suggestions in the news below (click more and you can leave comment for each release).

I have been seeing “setting a property that has only a getter error” poping up in my firebug for a while, which I believed was a Firefox extension conflict with new version of firebug.

A recent post to dojo-interest mailing list caught my eye: basically, a user can reproduce this problem by just loading dojo from google CDN.

I decided to take a look at this and try to figure out why.

A firebug bug report is filed about this error: with FireFox>3.5.2, modifying window.console (or attributes on console) would trigger this error. However, in the test case mentioned in the post, even if dojo is not loaded, the error still pops up in firebug, so it must be in some firefox extension, rather than dojo.

The only other extension I have in my development firefox profile is Selenium-IDE 1.0.4. Disabling it, and the error immediately goes away. Searching selenium-ide bug report, it turns out it has just been fixed in Selenium-IDE 1.0.5 (direct link to the xpi file).

In a summary, if you are getting “setting a property that has only a getter error” Error in FF 3.6 with any page, make sure you have at least Selenium-IDE 1.0.5. If you don’t use it, then you are probably messing around with window.console. (the error message would be much more helpful if it states what property is being accessed)

I have been seeing “setting a property that has only a getter error” poping up in my firebug for a while, which I believed was a Firefox extension conflict with new version of firebug.

A recent post to dojo-interest mailing list caught my eye: basically, a user can reproduce this problem by just loading dojo from google CDN.

I decided to take a look at this and try to figure out why.

A firebug bug report is filed about this error: with FireFox>3.5.2, modifying window.console (or attributes on console) would trigger this error. However, in the test case mentioned in the post, even if dojo is not loaded, the error still pops up in firebug, so it must be in some firefox extension, rather than dojo.

The only other extension I have in my development firefox profile is Selenium-IDE 1.0.4. Disabling it, and the error immediately goes away. Searching selenium-ide bug report, it turns out it has just been fixed in Selenium-IDE 1.0.5 (direct link to the xpi file).

In a summary, if you are getting “setting a property that has only a getter error” Error in FF 3.6 with any page, make sure you have at least Selenium-IDE 1.0.5. If you don’t use it, then you are probably messing around with window.console. (the error message would be much more helpful if it states what property is being accessed)

I have been seeing “setting a property that has only a getter error” poping up in my firebug for a while, which I believed was a Firefox extension conflict with new version of firebug.

A recent post to dojo-interest mailing list caught my eye: basically, a user can reproduce this problem by just loading dojo from google CDN.

I decided to take a look at this and try to figure out why.

A firebug bug report is filed about this error: with FireFox>3.5.2, modifying window.console (or attributes on console) would trigger this error. However, in the test case mentioned in the post, even if dojo is not loaded, the error still pops up in firebug, so it must be in some firefox extension, rather than dojo.

The only other extension I have in my development firefox profile is Selenium-IDE 1.0.4. Disabling it, and the error immediately goes away. Searching selenium-ide bug report, it turns out it has just been fixed in Selenium-IDE 1.0.5 (direct link to the xpi file).

In a summary, if you are getting “setting a property that has only a getter error” Error in FF 3.6 with any page, make sure you have at least Selenium-IDE 1.0.5. If you don’t use it, then you are probably messing around with window.console. (the error message would be much more helpful if it states what property is being accessed)

I have been seeing “setting a property that has only a getter error” poping up in my firebug for a while, which I believed was a Firefox extension conflict with new version of firebug.

A recent post to dojo-interest mailing list caught my eye: basically, a user can reproduce this problem by just loading dojo from google CDN.

I decided to take a look at this and try to figure out why.

A firebug bug report is filed about this error: with FireFox>3.5.2, modifying window.console (or attributes on console) would trigger this error. However, in the test case mentioned in the post, even if dojo is not loaded, the error still pops up in firebug, so it must be in some firefox extension, rather than dojo.

The only other extension I have in my development firefox profile is Selenium-IDE 1.0.4. Disabling it, and the error immediately goes away. Searching selenium-ide bug report, it turns out it has just been fixed in Selenium-IDE 1.0.5 (direct link to the xpi file).

In a summary, if you are getting “setting a property that has only a getter error” Error in FF 3.6 with any page, make sure you have at least Selenium-IDE 1.0.5. If you don’t use it, then you are probably messing around with window.console. (the error message would be much more helpful if it states what property is being accessed)

I have been seeing “setting a property that has only a getter error” poping up in my firebug for a while, which I believed was a Firefox extension conflict with new version of firebug.

A recent post to dojo-interest mailing list caught my eye: basically, a user can reproduce this problem by just loading dojo from google CDN.

I decided to take a look at this and try to figure out why.

A firebug bug report is filed about this error: with FireFox>3.5.2, modifying window.console (or attributes on console) would trigger this error. However, in the test case mentioned in the post, even if dojo is not loaded, the error still pops up in firebug, so it must be in some firefox extension, rather than dojo.

The only other extension I have in my development firefox profile is Selenium-IDE 1.0.4. Disabling it, and the error immediately goes away. Searching selenium-ide bug report, it turns out it has just been fixed in Selenium-IDE 1.0.5 (direct link to the xpi file).

In a summary, if you are getting “setting a property that has only a getter error” Error in FF 3.6 with any page, make sure you have at least Selenium-IDE 1.0.5. If you don’t use it, then you are probably messing around with window.console. (the error message would be much more helpful if it states what property is being accessed)

I have been seeing “setting a property that has only a getter error” poping up in my firebug for a while, which I believed was a Firefox extension conflict with new version of firebug.

A recent post to dojo-interest mailing list caught my eye: basically, a user can reproduce this problem by just loading dojo from google CDN.

I decided to take a look at this and try to figure out why.

A firebug bug report is filed about this error: with FireFox>3.5.2, modifying window.console (or attributes on console) would trigger this error. However, in the test case mentioned in the post, even if dojo is not loaded, the error still pops up in firebug, so it must be in some firefox extension, rather than dojo.

The only other extension I have in my development firefox profile is Selenium-IDE 1.0.4. Disabling it, and the error immediately goes away. Searching selenium-ide bug report, it turns out it has just been fixed in Selenium-IDE 1.0.5 (direct link to the xpi file).

In a summary, if you are getting “setting a property that has only a getter error” Error in FF 3.6 with any page, make sure you have at least Selenium-IDE 1.0.5. If you don’t use it, then you are probably messing around with window.console. (the error message would be much more helpful if it states what property is being accessed)

I have been seeing “setting a property that has only a getter error” poping up in my firebug for a while, which I believed was a Firefox extension conflict with new version of firebug.

A recent post to dojo-interest mailing list caught my eye: basically, a user can reproduce this problem by just loading dojo from google CDN.

I decided to take a look at this and try to figure out why.

A firebug bug report is filed about this error: with FireFox>3.5.2, modifying window.console (or attributes on console) would trigger this error. However, in the test case mentioned in the post, even if dojo is not loaded, the error still pops up in firebug, so it must be in some firefox extension, rather than dojo.

The only other extension I have in my development firefox profile is Selenium-IDE 1.0.4. Disabling it, and the error immediately goes away. Searching selenium-ide bug report, it turns out it has just been fixed in Selenium-IDE 1.0.5 (direct link to the xpi file).

In a summary, if you are getting “setting a property that has only a getter error” Error in FF 3.6 with any page, make sure you have at least Selenium-IDE 1.0.5. If you don’t use it, then you are probably messing around with window.console. (the error message would be much more helpful if it states what property is being accessed)

I have been seeing “setting a property that has only a getter error” poping up in my firebug for a while, which I believed was a Firefox extension conflict with new version of firebug.

A recent post to dojo-interest mailing list caught my eye: basically, a user can reproduce this problem by just loading dojo from google CDN.

I decided to take a look at this and try to figure out why.

A firebug bug report is filed about this error: with FireFox>3.5.2, modifying window.console (or attributes on console) would trigger this error. However, in the test case mentioned in the post, even if dojo is not loaded, the error still pops up in firebug, so it must be in some firefox extension, rather than dojo.

The only other extension I have in my development firefox profile is Selenium-IDE 1.0.4. Disabling it, and the error immediately goes away. Searching selenium-ide bug report, it turns out it has just been fixed in Selenium-IDE 1.0.5 (direct link to the xpi file).

In a summary, if you are getting “setting a property that has only a getter error” Error in FF 3.6 with any page, make sure you have at least Selenium-IDE 1.0.5. If you don’t use it, then you are probably messing around with window.console. (the error message would be much more helpful if it states what property is being accessed)

I have been seeing “setting a property that has only a getter error” poping up in my firebug for a while, which I believed was a Firefox extension conflict with new version of firebug.

A recent post to dojo-interest mailing list caught my eye: basically, a user can reproduce this problem by just loading dojo from google CDN.

I decided to take a look at this and try to figure out why.

A firebug bug report is filed about this error: with FireFox>3.5.2, modifying window.console (or attributes on console) would trigger this error. However, in the test case mentioned in the post, even if dojo is not loaded, the error still pops up in firebug, so it must be in some firefox extension, rather than dojo.

The only other extension I have in my development firefox profile is Selenium-IDE 1.0.4. Disabling it, and the error immediately goes away. Searching selenium-ide bug report, it turns out it has just been fixed in Selenium-IDE 1.0.5 (direct link to the xpi file).

In a summary, if you are getting “setting a property that has only a getter error” Error in FF 3.6 with any page, make sure you have at least Selenium-IDE 1.0.5. If you don’t use it, then you are probably messing around with window.console. (the error message would be much more helpful if it states what property is being accessed)

I have been seeing “setting a property that has only a getter error” poping up in my firebug for a while, which I believed was a Firefox extension conflict with new version of firebug.

A recent post to dojo-interest mailing list caught my eye: basically, a user can reproduce this problem by just loading dojo from google CDN.

I decided to take a look at this and try to figure out why.

A firebug bug report is filed about this error: with FireFox>3.5.2, modifying window.console (or attributes on console) would trigger this error. However, in the test case mentioned in the post, even if dojo is not loaded, the error still pops up in firebug, so it must be in some firefox extension, rather than dojo.

The only other extension I have in my development firefox profile is Selenium-IDE 1.0.4. Disabling it, and the error immediately goes away. Searching selenium-ide bug report, it turns out it has just been fixed in Selenium-IDE 1.0.5 (direct link to the xpi file).

In a summary, if you are getting “setting a property that has only a getter error” Error in FF 3.6 with any page, make sure you have at least Selenium-IDE 1.0.5. If you don’t use it, then you are probably messing around with window.console. (the error message would be much more helpful if it states what property is being accessed)