Codes R&D management platform open source version 4.2.0 released

1: Introduction to codes

Codes is an efficient, simple and lightweight one-stop R&D management platform. Including requirements management, task management, test management, defect management, automated testing, cicd and other functions; Codes helps enterprises accelerate the integration of R&D, testing, operation and maintenance. Under normal circumstances, the slash-and-burn Test link has been stepped down by automated Dev and Ops. brake. Codes focuses on the tests with the weakest technology and least attention, and breaks through the lubricating link between R&D and operation and maintenance through implementation of agile testing. It solves the barrel effect of Test in the rapid iteration of DevOps and promotes the integration process of R&D, testing, and operation and maintenance. The commercial version has no function limit, local installation is limited to the number of users, and 30 users are free ; The community version currently only opens test tracking management (main function use case management , defect management), and then separate other functional codes.

Codes helps IT companies digitally transform and achieve cost reduction and efficiency increase; it provides managers with a God's perspective view of the entire software development process in a convenient way; it allows executives to collaborate efficiently without increasing burdens, making it easy to find the right person for the execution process. Transparent and traceable; all R&D activities are unified around needs, and business data in all scenarios are always connected and not separated.

office icodes.work

Two: 4.20.5 update instructions

The main investigation is bug fixing, a total of 20 bug fixes, plus 2 minor updates

Version 4.2.0 2 updates:

1. In versions before 4.2.0, you can fill in progress and execute test package use cases on the dashboard. This time, you can handle BUGs that are transferred to your name on the dashboard
2 , Task statistics SQL optimization in test overview

Version 4.2.0 20 bugs fixed:

1. When iteratively allocating test packages, the grigd list is loaded twice
2. When only participating in one project, when clicking the "Test" menu, there is an additional query for participating projects< /span>20. Enter the use case package and click the first one to execute, then directly click the next one to the second one, and click Pass. That is to say, the first one is opened but not executed, and then the next one is clicked again. Execution, the execution rate is wrong19. On the test case page, the grid on the left and the tree on the right are not the same height18. Test overview, under chrome (win10 1920* 1080), project staff summary, number of pending bugs, cannot be seen, you need to zoom the browser to 90% to display it17. Add a user, then delete it, then select another user, and then click Modify, it keeps prompting to select a record16. Add a group, then delete it, then select another group, and then click Modify. It keeps prompting you to select a record, such as the maintenance personnel. The maintenance is unsuccessful and there is an error in JS14. The number of all tasks of the current project counted in the test overview is incorrect13. When only participating in one project, the display is normal when clicking the "Test" menu, and then switch to Other menus such as iteration, when switching back, there are two left menus that are selected12. In the BUG list, select a BUG and modify it , select another BGU, and when you click modify, it always prompts you to select the record to be modified11. Process the BUG in iteration, set it to repeat, and then associate the repeated BUG. JS reports an error that the variable has not been resolved, and the entire page is stuck10. In the BUG process settings, set the follower, check the follower process, and choose to notify the project follower. When submitting, it always prompts you to select 9. When it is set to have a bug transferred to the developer's name, no emails will be sent, and when the bug is processed, a system error will be reported8. In the BUG In the list, quickly check a BUG with the number, then modify the BUG and close the submission. The page is refreshed, but when you select the first BUG in the BUG table and click Modify, it keeps prompting you to select the record to be modified. If you select something other than the first one, One is normal 7. Development A set a certain BUG to "Pending/Modified in the next version", R&D Manager (Arbitrator), agreed that the next version modification setting is "to be changed/modified in the next version". When developer A wanted to deal with this BUG in the next version, the prompt was not transferred to him6. On the Kanban board, non-managers select projects At that time, some tasks that were not related to any project were also found. 5. On the Kanban board, when selecting a project, the iteration data under it cannot be found, and an SQL error is reported in the background4. Non-administrators are here. When viewing task details on the dashboard, the person in charge and the project they belong to are Empty
3. Test requirements management, the grid list is loaded twice















Three: Screenshot of functional interface

Conduct multi-dimensional analysis of full-scenario R&D data to help teams continuously improve efficiency and help companies deepen R&D efficiency

 

The integration of agile and waterfall, there are iterations and milestones that the PMO focuses on

To-do ranking, you can see the current progress bottleneck at a glance

The workload is displayed in the form of calendar and Gantt chart, which is intuitive and fast

Testing, development, product output and working hours are clear at a glance

Generative global Kanban board, define Kanban board through query conditions, and can customize different queries and save them

Multiple view modes to meet different needs, unify all R&D activities around needs, ensure alignment of stakeholder information, and achieve linkage of major R&D activities on one page

There are useful tasks or sub-requirements under the requirement. Use the working hours of the task or sub-requirement to calculate the working hours of the parent requirement. If you need to pay more attention, it can also be calculated layer by layer.

Multi-item iteration, from requirements to testing to online open and closed loop

After the requirements are reviewed, they are planned into iterations, and then the developers split the requirements into tasks, while testing and writing test cases, and the output in the process is placed in

The iterative deliverables are automatically associated with the project documents, and the online items and executors are defined in the release when they are online.

Align all R&D activities around needs

 

Tasks under iteration or tasks in task management can be grouped and displayed based on the person in charge, task type, priority, and requirements.

 

Daily reports are integrated with working hours, and working hours are filled in in batches in minutes, making annoying working hours no longer annoying!

The items of the day are automatically listed, and the working hours are filled in afterwards. The working hours are calculated for defects and use cases, and the iteration progress, project progress, and department working hours can be fully counted. Drill down to people according to the support levels, such as drilling down from the project to the iteration, and then drill down from the iteration to the person, or drill down from the department to the person

 

 

Organize testing in an iterative manner, which is easier to manage than traditional test plans

Zero-code drag-and-drop implementation of code compilation and deployment

Zero-code drag-and-drop interface automation arrangement

Automatically derive the interface dependency topology relationship diagram, making the interface relationship no longer a black box, and a convenient interface call chain

Drag and drop to generate assertions and drag and drop to extract parameters, making interface testing foolproof; innovative interface chaos testing to complete interface robustness testing in an instant.

Finally, let’s make a summary: Illustrated Codes

Guess you like

Origin www.oschina.net/news/271219/codes-4-2-0-released