Background reply " 1024 " there is a surprise, you know
Read this article takes about 5 minutes.
As already wrote three articles on software testing experience map, have not seen the students please come quickly review the following links point Ha:
" How to help complete summary of test experience profiles for three months? "
" Talk about software testing experience map "
" Software testing experience atlas hard skills of business logic ."
Continue topic before, and today we talk about the main map software testing experience hard skills branches testing skills, look at my broken mind map:
In the figure, based on my own project experience and basic theory of software testing, the testing experience is divided into three blocks, namely: 需求质量、测试质量和发布质量.
Here we were to do some detail.
First, the demand for quality
No matter which software engineering software development process, software testing is still a few classic model, demand is always at the top, the demand is the foundation for all subsequent processes, but also the follow-up process to promote factual basis.
Since such a critical demand, then we as a software test engineer, how to ensure the effective demand for quality?
I already have three articles mentioned this matter in detail, please click on the following link to view:
" What is the value testers involved in needs assessment is? "
" Needs assessment of the practical exercise ."
" Needs assessment of the implicit demand "
Overall, that is, from 需求合理性and 需求全面性two aspects of safeguards demand quality.
Second, test quality
Quality assurance testing on the premise that demand quality, of course, there is a hidden quality development, if the pre-job role through the test yourself or let the quality of intervention in these two areas are effectively protected, then the test quality has been guaranteed.
毕竟软件质量不是测出来的，是所有人共同努力构建出来的，测试只是做一个检测和验证的过程。
具体到测试质量检测和验证的内容，就是目前测试工程师日常工作占时最大的部分，我给分为冒烟测试、测试计划、测试用例和测试总结这么几个部分。
冒烟测试的关注点就是前面说的需求质量和开发质量，具体要检测的内容包括但不限于：
1、需求实现不完全：没有做应该做的事；
2、需求实现超预期：做了不应该做的事；
3、主流程没跑通：联调失败；
4、基本功能实现有问题：低级错误；
等等，这些都可以按冒烟失败进行打回。
如果冒烟测试通过，测试人员就可以正式接收测试，这时候可以按照提前制定的（大部分是现在开始制定的）测试计划进行详细测试安排。
这个测试安排不是传统的非常详尽的周密计划，这里的核心体现为测试策略，就是时间安排、里程碑时间点确立、优先级划分、各种资源的协调等等。
有了测试计划这个明确的依据之后，就可以正式进入用例的环节了。
用例环节我又给分成用例编写、用例评审和用例执行三个环节。
注意这三个环节可以是连续的串行，也可以是并行，还可以是和需求推进实现的过程同步进行，这里仅仅汇总起来集中表示用例这个活动。
一个项目可以说因为需求简单，没有需求质量要求的环节，也没有测试计划，但是测试用例的环节是必不可少的，同时，一个测试人员的能力可以尽情的在测试用例环节中进行发挥，在这里，测试人员的水平可以立见高下。
关于测试用例的话题可以展开来说很多，本次主要说图谱，所以我还是按索引做个大概讲解，更详细的后续逐步完善。
比如测试用例编写常用的等价类、边界值等方法，后面会专门讲。
比如用例评审相关的用例格式和覆盖率可以看这几篇总结：
最后是用例执行部分，这个一方面需要执行人员结合测试策略进行灵活安排，另一方面需要执行人员有足够的专注度、发散思维、探索意识和问题敏感度，这样才能真正让测试质量过程起到检测和验证的效果。
三、发布质量
最后说一下发布质量。
说实话，很久前我对测试人员负责上线这件事一直耿耿于怀，我们不是测试么？我们应该把主要精力放到检测和验证上面呀，为啥测试通过的东西，还需要我们给发布到线上？
后来看问题的视角开阔了，才想明白发布质量这个概念，亦可以说是全流程质量这个概念。
质量保证是全流程的活动，是项目所有人员都需要关注的问题，既然是这样，测试去参与全流程的质量保证就是合理的了，有些地方可能只是参与，比如需求评审，比如单元测试，有些地方需要自己亲力亲为，比如接口测试，比如系统测试，再比如现在说的发布上线。
另外，这里说的发布质量并不单纯指发布上线这个动作，从导图可以看出来，我给分成了三部分，分别是上线质量、数据监控和反馈跟进，分别对应的是上线过程不同环节我们需要重点关注的内容。
当然，有些公司可能会有其他角色来参与发布质量的保障，比如产品会做数据监控、开发会做反馈跟进等等，那么测试可以根据实际情况决定自己去主导还是去辅助，总之，去参与这个过程可以从另一个角度去考虑质量保证的问题。
以上，今天的主要内容是软件测试经验图谱硬技能之测试技能，内容比较多，我只是提供了框架，后续对于需要细化的内容会有单独的文章，敬请期待。
Also be sure to know the map is not an end in itself, a more accurate self-awareness and self-improvement is the purpose of the aid map , the map only systematic software testing related skill requirements are summarized, we often need the aid of self-reflection profiles and continue to play to our strengths, and find ways to make up for our deficiencies, thus precipitating our working life as work experience.
Thank you for reading, please forward to help share the point of a + "look" to allow more people to see, thank you .
Thank you for sharing, and looking forward, I prepared a raffle, July 23 8:15 automatic lottery.
Thank you for reading, and looking forward, the point I draw, I wish you good luck!
Recommended reading:
Get the demand, how about writing a test case?
Remember once complete the process of solving the problem analysis
Reading "Jingdong quality real transition team" felt
How to use VM virtual machine port mapping for data forwarding
