I have done that Manuel :)

Great!

I would be perfect if you could update the developer guide to add the informations you wanted to have 2 days ago when you starting struggling with this issue

The local unit test completed successfully finally :)

I have pushed the necessary changes, right now my development setup is perfect as i am able to test successfully.

Thanks a lot Nicolas and Manuel, It was your constant support which helped me get out of the issues.

Ok I see the point.

Assuming that both folders (/home/centos/tuleap/dev and /usr/share/codendi) are on the same host, please run the following commands:
$ mv /usr/share/codendi /usr/share/codendi_rpm
$ ln -s /home/centos/tuleap/dev/ /usr/share/codendi

This 1) backups the codendi folder installed by the rpm and 2) links codendi to your development folder. That way you don't have to copy/paste every time your changes.

Initially the tests folder was missing under /usr/share/codendi/plugins folder, so i copied it from my git's branch which is under /home/centos/tuleap/dev/ folder(my .git is present here only, ie the git repository)

I push and pull from here only and then copy the changes from here to /usr/share/codendi/ path which is mapped to my localhost.

cat /usr/share/codendi/VERSION
gives
5.5.99.3
--------------------------------
ls -l /usr/share/codendi/src/common
gives
-rwxrwxrwx 1 root centos 1692 Aug 14 18:06 autoload_zend.php
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 backend
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 chart
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 collection
drwxrwxrwx 3 root centos 4096 Oct 9 19:00 dao
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 date
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 error
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 event
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 filter
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 frs
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 html
drwxrwxrwx 3 root centos 4096 Oct 9 19:00 include
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 language
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 layout
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 mail
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 mailing_list
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 mvc
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 mvc2
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 password
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 permission
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 plugin
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 project
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 reference
drwxrwxrwx 3 root centos 4096 Oct 9 19:00 rss
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 server
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 session
drwxrwxrwx 3 root centos 4096 Oct 9 19:00 soap
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 survey
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 svn
drwxrwxrwx 3 root centos 4096 Oct 9 19:00 system_event
drwxrwxrwx 3 root centos 4096 Oct 9 19:00 templating
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 tracker
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 TreeNode
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 user
drwxrwxrwx 2 root centos 4096 Oct 9 19:00 valid
drwxrwxrwx 2 root centos 4096 Nov 28 22:06 widget
drwxrwxrwx 6 root centos 4096 Oct 9 19:00 wiki
----------------------------------------------------------------------------
uname -a
gives
Linux tuleapalm.somnath.loc 2.6.18-308.16.1.el5 #1 SMP Tue Oct 2 22:01:37 EDT 2012 i686 i686 i386 GNU/Linux
----------------------------------------------------------------------------
rpm -qa | grep release
gives
centos-release-notes-5.8-0
centos-release-5-8.el5.centos
----------------------------------------------------------------------------
php -v
gives
PHP 5.1.6 (cli) (built: Jun 27 2012 12:21:16)
Copyright (c) 1997-2006 The PHP Group
Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies

What is the result of those commands?

$ cat /usr/share/codendi/VERSION
$ ls -l /usr/share/codendi/src/common
$ uname -a
$ rpm -qa | grep release
$ php -v

Nicolas,
I am able to test it now, it requires https:// instead of http:// in my case.
Running the test locally gives the following result(ie. by running plugins/tests/ url):

Warning: require_once(common/autoload.php) [function.require-once]: failed to open stream: No such file or directory in /usr/share/codendi/plugins/tests/www/tests_common.php on line 39

Fatal error: require_once() [function.require]: Failed opening required 'common/autoload.php' (include_path='/usr/share/pear/:/usr/share/codendi/src/www/include:/usr/share/codendi/src:.:/usr/share/codendi/src:/usr/share/codendi/src/www/include:/usr/share/htmlpurifier:/usr/share/jpgraph') in /usr/share/codendi/plugins/tests/www/tests_common.php on line 39

What the logs are saying when you hit the plugins/tests/ url? access_log ? error_log ?

Running:
ls -dl /usr/share/codendi/plugins/tests
gives
drwxrwxr-x 7 centos centos 4096 Dec 7 11:25 /usr/share/codendi/plugins/tests

Running:
ls -dl /usr/share/codendi
gives
drwxrwxrwx 10 root centos 4096 Dec 7 10:11 /usr/share/codendi

What is the results of those commands?

$ ls -dl /usr/share/codendi/plugins/tests
$ ls -dl /usr/share/codendi

yes, i know that, i actually hit http://localhost/plugins/tests/ only, as my local setup of tuleap opens from localhost, but still it gives page not found.

> The browser says it is unable to resolve the hostname in my local set up for this http://tuleap.example.com/plugins/tests/.

Yes of course :) That was an example url. You have to replace tuleap.example.com with your own tuleap instance.

The browser says it is unable to resolve the hostname in my local set up for this http://tuleap.example.com/plugins/tests/.

My only error is as follows:
Error Message
tests/simpletest/LanguageFilesTest.php

Stacktrace
TuleapTestSuite -> tests/simpletest/LanguageFilesTest.php

Fail at [/data/jenkins/jobs/1926_login_to_post_a_new_thread/workspace/sources/tests/simpletest/LanguageFilesTest.php line 20]
Kindly let me know the possible reason for this error and how to do a unit test for this.

There is a typo in the developer guide. I've just fixed it.

The correct url for the tests is http://tuleap.example.com/plugins/tests/ (please note the ending '/')

As per the developer guide,
To run tests we can either use:

the web interface available at http://localhost/plugins/tests (given localhost is your development server)
or
the CLI interface: make tests (at the root of the sources)
You can run a file or a directory: php tests/bin/simpletest plugins/docman

Kindly help me out as this is the first time am testing.

The build fails because of the tests:
http://ci.tuleap.net/jenkins/job/1926_login_to_post_a_new_thread/2/testReport/?

You can reproduce it on your side by running unit test in local

-> for the job, you were supposed to click the "save" button a the very bottom of the page

Manuel,

The job is still failing as I can see.

Actually I clicked the Add button below after modifying "!!!!BRANCHNAME" before saving the job. So the fault was that I was not supposed to click the Add button right?

The error looks as if the job was not set-up correctly. Did you follow the steps in https://tuleap.net/wiki/index.php?group_id=101&pagename=Development%2FGitWorkflow ?

In Jenkins. ut_1926_login_to_post_a_new_thread job build is failing. Can i get a log for the reason of the failure?

Thanks Manuel,

Created a job under the name ut_1926_login_to_post_a_new_thread.

I granted you the right to create a jenkins job.

Hi Manuel,

I have pushed the changes under branch name "1926_login_to_post_a_new_thread".

Is it necessary to Create a CI job for that branch?
I have an account in jenkins under user id bistub1986 but don't have any job creation permission there.

Hi Biswajit,

You should have all the necessary informations to propose a branch into https://tuleap.net/wiki/?group_id=101&pagename=DeveloperGuide

I added you as member of Tuleap project as well as in the developer group.

Hi Nicolas,

I have been able to find the fix for this bug.
Please let me know where can I push this code fix.

Linked to art #1868