When I have not started working, I was full of the actual project development process and the unknown yearning, when it hopes to have a person come, tell me something about the actual work it is what it looks like.Now this blog is written for those friends or just practice immediately work is not work. We hope to have a preliminary knowledge and understanding of the development process.
Development process at work: (I am currently project like this.)
The overall process is as follows:
1. collar job
2. The development, self-test, submit code
3. Test to test, modify anti-Bug
First of all, the first step: collar tasks: We are using the nails graphite documents
Come in like this, above is the development progress of the developer, the following test schedule testers. Developers after the completion of their tasks to develop, test personnel table in progress, your module, to measure them
We are now the sixth milestone. This milestone is a functional module in accordance with customer requirements, after the first module to do the project on-line, first with the. Subsequent hair open slowly, iterative updating function
Then, points come in, find their task assignments, task manager for the project is good points.
After such a document you work, you should often come into contact, which is when many people work together to develop a more convenient function.
Code specific business logic, and functions, I will not elaborate, I can only talk about the overall process, let everyone have a total workflow concepts.
git everyone should be familiar with it, we are using GitLab warehouse. We have completed development of the project code in the repository.
git svn is an upgraded version of it. Better use. The code uses a distributed management.
Every themselves to establish their own branch, developed the code in their own branch, after the completion of the development, merged into the master branch of the project.
Multiplayer co-development, is relying on this tool to achieve. Background developer, that is, they are in the learning process should be to find out about it.
This is a development stage, to achieve specific functions and business logic, each company is different, I will not say.
After you complete function, how we can complete it? How to pass it? You could write a pile of garbage code and logic on the line yet?
然后 提交测试， 测试那边会有写好的测试用例和效果图 。接下来就是我列的技术列表里面的第八条了。
首先： sonarqube 软件 （当然，只是我们公司用的这一款， 这种软件特别多， 类别是：代码质量监控管理软件 ）。
在里面 设定你这个项目的项目规范， 比如简单的普遍的这种： 不允许存在未引用的导包代码， 名字命名规范，变量规范， 之类的。如图。
这些是 大佬级别的 项目经理 他们写好的， 开发人员 只是使用一下这个软件。架构师他们的工作。
这个软件 检查 你的代码质量。 当然 在IDEA里面有 sonar插件， 不知道大家用过没有 （类似于阿里巴巴开发规范的插件）
代码质量测试通过之后， 测试人员才会接下来去测试你的代码 和效果 逻辑什么的。
至于 第八条里面 另外一个提到的 JIRA， 是项目问题追测管理系统 ， 简单来说 ，就是测试人员发现的bug, 在这个软件里 提给你， 你去改bug。
里边是这样的。
就是使用这些软件， 你们看 ，你们没了解过， 别人问起来，你不知道， 就知道你没有协同开发过，如果没协同开发过 就知道你是个弟弟。
当然这个软件 也是能看一个人的bug 数，开发质量什么的用事实来说话。 以至于你以后赖账。 说这不是你的bug
还有这些，是测试案例，你的功能 都是可以看得到 列的出来的， 方便 项目经历管理。
开发完之后的代码。需要发版到客户那边， 由于我们这个服务器在台北 然后后面都是运维什么的事了。开发人员的工作到此结束。
里面用到的工具，部分我已经在上一篇贴子中有所简单的介绍，具体使用还请自行百度。