Zen defect management tool ---

Zen

1. Introduction Zen

1.1 Zen project management software is doing what?

Zen Qingdao Easy Soft Network Technology Development Co., day, domestic open source project management software. It combines product management, project management, quality management, document management, organizational management and transaction management in one, is a professional R & D project management software, complete coverage of the core process R & D project management. Zen results-oriented management thinking, full-featured rich, simple and efficient operation, beautiful interface, powerful search, statistical reports rich and diverse, rational software architecture, flexible expansion, improve the API can be called. Zen, focus on R & D project management!

Zen 1.2 Why the name?

Zen and Taoism word meaning extremely rich, has spiritual meaning, but also a cultural meaning level. Zen project management software, whichever is the cultural meaning, hope to convey our understanding and thinking on the management by the word. The name is subject to "programming of the Road" and "The Zen of programming" inspired by these books. English inside of Zen Zen, Taoism is Tao, so our software English name for zentao.

2. Installation Zen

2.1, a key installation package running windows

Double-decompression to the root of a partition, such as ** c: \ xampp, or d: \ xampp **, must be the root directory. Into the xampp folder, click start.exe start Zen, if the computer does not run through the VC environment installation, you will be prompted to install VC ++ environment.

Windows a key to run the installation package you need to install VC ++ environment.

 

 

 

2.2, modify the database password

Zen after the service starts, you will be prompted database password is too weak, it is recommended to change the password.

Will display a default password, you can also set yourself a password, the password database is automatically modified click OK.

​ 

 

 

 

2.3 Apache, user access authentication

After the start Zen, it is enabled by default the Apache user access authentication. If you do not want to open, you can not directly check to.

 

 

 

2.4, launch and access Zen

After starting the control panel, click on the "Zen start" button, the system will start apache and mysql services needed Zen automatically.

After a successful start, click on the "Access Zen", you can open the Home Zen environment. Etc. After the meeting, the page will automatically jump to the page Zen log in, the default administrator account: admin, password: 123456, log in to change password, administrator password must remember.

 

 

 

3. The use of Zen

 

 

 

3.1 Change Password strength check 

3.2 Creating departments and user roles; Note: the super administrator role is to log on

3.3 Product Manager to create products for their needs; Note: Product Manager role to log on to operate

(1), the establishment of product; (2) establishing module; (3) the establishment plan; (4), put forward the demand ( demand audit status are: Active; otherwise it is a draft state); (5), needs assessment and change Request

1. Product Review is unaudited demand for by the conduct that the state needs a "draft"

    

   note:

   • If you choose to "be clear", it will remain a draft state demand, and demand is assigned back to the creator of the head of the demand, which has continued to improve.
   • If "reject", then gives the corresponding need to reject cause, reject reasons are:

2. Change and assessment requirements

   Everything on demand title, description, modify the authentication standard, the attachment can be changed demand, the state after the change is the change in.

   

    

    

    

   If you choose does not need to review the changes, the demand state is activated

3.4 Project Manager to create a project, the association needs

Note: the project manager role login operation

(1) Project project

Project approval is confirmed by the meeting, prepared in advance by the project manager, told the team meeting the specific time and place, prior to the project manager needs to be divided, the association will issue needs to be achieved to the project,

Product manager needs to explain, participants put forward their views on the needs of employees, the explanation is completed, the workload to assess and prioritize the needs of each, and then the size of the workload according to priority needs, the needs do adjusted accordingly, will not require advance of demand delayed development.

(2) the project manager to create a project, the association needs

(3) Set up your development team project manager

After the project is created, you will be prompted to set team

Or, from the Project View menu team can also manage a team of project

(4) the project manager task decomposition

Association, decomposition demand

Demand: Demand for the decomposition of particle size as small as possible

3.5 Development to receive the task, be measured mention

Note: All operations are under their own login account in developer operations

(1) Developers receive the task to confirm hours

Note: The general situation is developing the project managers to assign tasks and developers can log into your account to see their task as long as the modification task status from the beginning to be in, when the end of the state of development has been completed.

(2) Developers Create Version

When all the tasks developed, will be integrated in the git version, then there are specialized personnel mentioned measure, the general operation is leader

Create a complete version after version details page you can see the corresponding demand or bug

(3) provide for measurement

3.6 testers develop test cases, submitting bug, regression testing

(1), create, execute test cases

Write test cases in a test case details page

(2), implementation of test cases

1. Test case review

2. Associated version

3. Implementation of test cases

(3) Submit bug

option to submit bug bug

note:

• After submitting the test, testers test deployed, there will be bug generated. An important role of research and development team at this time is to solve the bug.

• Testers submit bug => developer to resolve the bug => testers verify the shut down, which is more normal flow. There is a flow activation process: testers submit bug => developer to resolve the bug => testers did not pass the verification => activation bug => readdress => Verify closed.

• Developers need to do is to be responsible for handling its own bug, and registered in Zen Solutions

(4), regression testing

step:

1. Developers enter the bug details page for confirmation, and then modify the code under the line of bug fixes, and unit testing, no problem, closed bug
2. Closed bug bug does not appear in the list, were closed for the bug testers test, the test is not by adding, to re-open the bug, and assigned to the relevant developers

to sum up

Zen is the largest defect management tool used for testing, testers must master the use of parts other appropriate roles to understand.

Testers are mainly used:

1. write test cases, test case execution

2. For the test fails, a bug filed, assigned to a respective developer

3. After the bug fixes developer timely test again, the test passes closed, otherwise it becomes active again