CHAMIKA KASUN


A wiki enables communities to write documents collaboratively, using a simple markup language and a web browser. A single page in a wiki website is referred to as a "wiki page", while the entire collection of pages, which are usually well interconnected by hyperlinks, is "the wiki". A wiki is essentially a database for creating, browsing, and searching through information. A wiki allows for non-linear, evolving, complex and networked text, argument and interaction.[6]

A defining characteristic of wiki technology is the ease with which pages can be created and updated. Generally, there is no review before modifications are accepted. Many wikis are open to alteration by the general public without requiring them to register user accounts. Many edits can be made in real-time and appear almost instantly online. This can facilitate abuse of the system. Private wiki servers require user authentication to edit pages, and sometimes even to read them.

Maged N. Kamel Boulos, Cito Maramba and Steve Wheeler write that it is the "openness of wikis that gives rise to the concept of 'Darwikinism', which is a concept that describes the 'socially Darwinian process' that wiki pages are subject to. Basically, because of the openness of wikis and the rapidity with which wiki pages can be edited, the pages undergo a natural selection process like that which nature subjects to living organisms. 'Unfit' sentences and sections are ruthlessly culled, edited and replaced if they are not considered 'fit', which hopefully results in the evolution of a higher quality and more relevant page. Whilst such openness may invite 'vandalism' and the posting of untrue information, this same openness also makes it possible to rapidly correct or restore a 'quality' wiki page."[7]

Read More …

Introduction
Testing programs is a boring thing.It takes lot of time and efforts to do that
but there are easier ways to do that by automated software one such great software is HttpUnit.
Introduction
HttpUnit is an open source software testing framework used to perform testing of web sites without the need for a web browser.
HttpUnit is primarily designed for "black-box" testing of web sites.
HttpUnit is free software available from HttpUnitSite that implements several useful unit testing methods together with classes for connecting to HTTP servers, processing HTML, and maintaining stateful sessions.

HttpUnit supports :
  • HTML form submission
  • JavaScript
  • automatic page redirection and cookies.
  • Written in Java, HttpUnit allows Java test code to process returned pages as text, XML DOM, or containers of forms, tables and links
It is well suited to be used in combination with JUnit.It easily write tests that verify the proper behaviour of a web site.The use of HttpUnit allows for automated testing of web applications.

The center of HttpUnit is the WebConversation class, which takes the place of a browser talking to a single site.It is responsible for maintaining session context, which it does via cookies returned by the server.To use it, one must create a request and ask the WebConversation for a response.

Some Drawbacks to HTTPUnit:
  • Tests are tied to page structures.
  • If you change your page (say, reordering links or forms), you will break your tests.
  • Test assertions typically depend on the content of the page.
  • If content changes, tests may break.
  • Checking content is not completely sufficient for testing Grid portals.

Setting HttpUnit in Oracle JDeveloper

One way to test Web application is with HttpUnit framework that is based on Junit. One nice thing about JDeveloper is that because of the built-in support for JUnit you also get a nice HttpUnit testing environment.

Here are the steps to follow.

1. Download HttpUnit and extract it to your drive.

2. In JDeveloper take your Web project and go into project properties->libraries. Click the "Add JAR" button and add the files from the lib and jars directory.




3. Create a new JUnit test case class:



4. Run your test:



5. View the results:



6. If you have errors double click the row in the JUnit log window to jump to the actual test code that failed.



Read More …