TestPlan clone with keep the attachment (checkbox checked) will raise error(duplicate primary key). Hence need add id (primary key) field.

You are trying to install wadostuff from https://wadofstuff.googlecode.com/files/wadofstuff-django-serializers-1.1.0.tar.gz#egg=wadofstuff-django-serializers which no longer works. Since this is only needed for such an old Django version, I think it makes sense to vendor https://github.com/mattimustang/wadofstuff/tree/master/python/serializer till you can move to 1.8

use south manage db migration

There are some user related form fields (e.g. Owner field in edit plan page), It's better that supporting auto-complete in such field.

After checked several tags, the filter result(e.g testcase) shoud include all the checked tags.

It would be great if new products, product version and plan types can be added when a test plan is being edited. In other words, the test plan edit page should behave more like the page for adding test plans.

• Copy the component to new product you specific (Unchecking will remove component of copied test case)
• Copy the attachments to new product you specific (Unchecking will remove attachments of copied test case)

@jianchen2580

There are some file upload page in nitrate, some pages need click the upload button and jump to a file upload page while others upload directly. I think it's no need that jump to a unify upload page.

w3m is an executable program. this is used for getting the content rendered from HTML content generated by TinyMCE. This is rely on the removal of TinyMCE. When TinyMCE is removed from Nitrate, we can remove w3m also.

Related to #1

Obvisouly, RESTful API is a must-have cool feature for wide various areas.

RESTful API aims to expose all necessary resources of Nitrate to all potential audiences, application development, etc. It is not intended to replace current XMLRPC API, that has been developing and using in production in the past years, and is still serving users now. However, XMLRPC is really an old technology, in contrast RESTful API is much modern way to expose internal resources and business to external world.

Resources and actions follows. This is an absolute draft. Continue to complete. Feel free to comment and make changes if necessary.

Authentication

Candidate authentication mechanisms

• Kerberos
• others?

TestPlan

• create: POST, /plans/create/
• delete: POST, /plans/\d+/delete/
• update: PUT, /plans/\d+/update/
• get an existing TestPlan: GET, /plans/\d+/
• search, pagination support: GET, /plans/search/
  Arguments: ?
• add cases to: PUT, /plans/\d+/cases/add/
• remove cases from: POST, /plans/\d+/cases/remove/

TestCase

• create: POST, /cases/create/
• delete: POST, /cases/\d+/delete/
• update: PUT, /cases/\d+/update/
• get an existing TestCase: GET, /cases/\d+/
• search, pagination support: GET, /cases/search/
  Arguments: ?

TestRun

• create: POST, /runs/create/
• delete: POST, /runs/\d+/delete/
• update: PUT, /runs/\d+/update/
• get an existing TestCase: GET, /runs/\d+/
• search, pagination support: GET, /runs/search/
  Arguments: ?
• add cases to: PUT, /runs/\d+/cases/add/
• remove cases from: POST, /runs/\d+/cases/remove/

TestCaseRun

• search, pagination support: GET, /case-runs/search/
  Arguments: ?
• status modification: POST, /case-runs/\d+/change-status/
• status modification can be expanded to several requests of each status for convenience
  • POST, /case-runs/\d+/idle/
  • POST, /case-runs/\d+/run/
  • POST, /case-runs/\d+/pass/
  • POST, /case-runs/\d+/pause/
  • ... where using verb. instead of a noun. to represent an action

Attachment of TestPlan, TestCase, TestCaseRun

Logs

Reference Links of TestCaseRun

• get list of reference links: GET, /test-case-runs/\d+/reference-links/
• add: POST, /test-case-runs/\d+/reference-links/add/
• update: POST, /test-case-runs/\d+/reference-links/\d+/update/
• delete: POST, /test-case-runs/\d+/reference-links/\d+/delete/

Product

• add: POST, /products/add/
• update: POST, /products/\d+/update/
• delete: POST, /products/\d+/delete/
• search: GET, /products/search/
  Arguments: ?

For convenience, following interfaces are to get all Product-specific resources. All are paginatable.

• search related TestPlans: GET, /products/\d+/plans/

TestCaseCategory

TestPlanType

other resources ? ...

add docs link in README.

Long time past, a test case' change log is displayed in a non-readable way. it's hard to read, and difficult to get the information about what is changed. A change log table would be a good way to display. for example,

The whitespace will block the json parse.

Test case and test plan should be routed via a human-readable link besides the ID, and this should be the default.

@jianchen2580
@BrickXu

Hi guys, do you still remember how to run tests? I run the tests in either

make test

or

./manage.py test --settings=tcms.settings.test

Lots of errors and failures. Looks something wrong of the way I run the tests. Need your help. Thanks.

I suggest removing kerberos dependency from repo.

CheckList:

• New application registry logic, need to handle the duplicated labels in INSTALLED_APPS. Refs https://docs.djangoproject.com/en/1.7/ref/applications/
• Upgrade 3rd libs.
• schema migrate scripts.
• Nitrate custom comments app will cause "maximum recursion depth exceeded" error.
• django.utils.simplesjon was removed, use json or simplejson instead.

Lots of view functions handle GET and POST both, it is not a good practice, need to do some refactoring to split GET and POST into different method.

Current changelog layout is not readable.

Many configuration are set in settings files. It would be better to make them configurable in Nitrate so that it's not necessary to restart whole application when making any changes.

Currently, following configuration can be made as configurable in Nitrate

• email
• Bugzilla
• JIRA
• Kerberos realm

please add others that could be done.

Currently, TestCase Change Logs is broken which only log a part of column transformation with awful format.

Nitrate currrently is running under Python 2.6 and 2.7. Although they are quite same, still small differences there. Anyway, the point of this issue is that multiple Python versions support is a great enhancement to ensure each release is compatible with the major Python versions being used in the community.

EDIT:

Python: 2.7, 3.5
Django: 1.8, 1.9, 1.10

After changing a test case run's status, log is Field case_run_status changed from IDLE to 8., where 8 should be the status name rather than its id.

Apply change log for every input, include WebUI and XMLRPC.

Support some command line tools to revert the data from change log, specially, user could specify table and column, with tester, manager, timestamp.

Markdown would be a good choice.

The origin design of Show-More confuses many users, and this is not consistent with other similar features that all of them are implemented in pagination.

This comes from https://fedoraproject.org/wiki/Tcms_feature_requirements

Integration with FAS would benefit Fedora QA to use Nitrate as their TCMS

Nitrate was being developed with old version of Python and Django for a long time. Now, we have no reason to keep these old technologies continously, no matter the enhancement supplied by newer release of Python and Django, or the security fixes especially from Django that should benefit any potential users.

Propose version of Python is 2.7, then Django version is 1.7.1 that is the latest released version as of writing this issue.

I have to say I'm not much radical to use most latest technology. That will introduce various problems to either development team and users. Supporting current widely-used technologies is accpetable. Meanwhile, a stable and explicit regular upgrade policy is important.

First step is to enable travis-ci and run flake8 check.

Nowadays, Nitrate needs a new and modern interface design, that is the revolution to current old design. It should be much easier to use than now, and be usable in mobile and modern web browser.

Requirement management is useful for a testcase management system.

1. support Requirement doc input
2. requirement could split to items which could link to specific testcase.
3. test report need support test coverage.

Currently, we difine search_fields in app/admin.py like:
search_fields = (('name', 'pk',)) which raise error like "FieldError: Cannot resolve keyword "('name', 'pk')" into field...."

There are several tab pages within a TestPlan page. Opening a TestPlan is a common operation to users, and usually Cases is the default tab to open. In this case, at the most of time, it's unnecessary to open other tabs to waste resources, and this will boost Nitrate to open a TestPlan and give a quick response.

After separating those to standalone pages, it also helps to apply cache policy upon those are not used frequently.

Curerntly, 1.6.11 would be a good choice to upgrade underlying Django as the first step. Because, 1.6.x is the last version to support Python 2.6.

Hello, I meet one error when I install the TCMS in CentOS 6.7 according to the installing guide.
你好，我按照安装文档在centOS 6.7上安装TCMS遇到如下错误。失败的步骤在这一步 Install from source code

error message below:
报错信息如下：

zip_safe flag not set; analyzing archive contents...
tcms.wsgi: module references __path__
tcms.xmlrpc.__init__: module references __path__
tcms.settings.common: module references __file__
creating 'dist/nitrate-3.8.17-py2.6.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing nitrate-3.8.17-py2.6.egg
removing '/usr/lib/python2.6/site-packages/nitrate-3.8.17-py2.6.egg' (and everything under it)
creating /usr/lib/python2.6/site-packages/nitrate-3.8.17-py2.6.egg
Extracting nitrate-3.8.17-py2.6.egg to /usr/lib/python2.6/site-packages
nitrate 3.8.17 is already the active version in easy-install.pth

Installed /usr/lib/python2.6/site-packages/nitrate-3.8.17-py2.6.egg
Processing dependencies for nitrate==3.8.17
Searching for kombu>=3.0.34,<3.1
Reading http://pypi.python.org/simple/kombu/
Best match: kombu 3.0.35
Downloading https://pypi.python.org/packages/5f/4f/3859b52f6d465d0d4a767516c924ee4f0e1387498ac8d0c30d9942da3762/kombu-3.0.35.tar.gz#md5=6483ac8ba7109ec606f5cb9bd084b6ef
Processing kombu-3.0.35.tar.gz
Running kombu-3.0.35/setup.py -q bdist_egg --dist-dir /tmp/easy_install-_Oe5Dn/kombu-3.0.35/egg-dist-tmp-jD87MN
error: /tmp/easy_install-_Oe5Dn/kombu-3.0.35/requirements/default.txt: No such file or directory
[root@baidu-mgame-online-cq02bcconline1395-1v4-4-1 Nitrate]#

My steps like below:
我的执行步骤如下：

git clone the respository to local.

• clone仓库到本地

git clone https://github.com/Nitrate/Nitrate.git

install the system dependences with root user

• 用root用户安装的系统依赖

yum install gcc w3m python-devel mysql-devel krb5-devel libxml2-devel libxslt-devel

install the python dependences with root user

• 用root用户安装的python依赖

pip install -r requirements/base.txt

meet errors when executing the following command in the repository directory.

• 在clone下来的仓库目录执行如下操作时报错了

python setup.py install

I find that the errors do not impact my following operations. I can run the TCMS service successfully even if the errors pop up.

Currently, the default Text editor is tinymce which is not 'user friendly' for the engineer. I think we should replace the tinymce editor with markdown.

Besides QPID, it would make Nitrate more usable by supporting more messaging brokers, e.g.

• fedmsg
• ZeroMQ
• RabbitMQ
• ActiveMQ

So far, Nitrate only needs to send messages.

Refer to https://travis-ci.org/Nitrate/Nitrate/jobs/118071150

Currently, 1.9.12 is okay.

This should be done after #113

UPDATE:

Upgraded to Django 1.10.8 eventually.

Seems qpid MQ is not main stream any more, we could support more main stream message queue like zeroMQ or rabbitMQ.