问题

如何编写测试用例?

  • 2023年5月2日
  • 2回答
  • 65的浏览量
IOan
Userlevel 4
徽章 + 3
  • IOan
  • 0.8跨声速
  • 6个回答

我想问一个问题,既简单又复杂的回答:你如何写测试用例?

为什么我说这是简单吗?

我的意思是根据一些定义测试人员编写测试用例,因为他们通常应该很容易。也有大量的信息在网上如何编写一个测试用例,它应该包含什么,所以,容易和简单。

为什么我说它是复杂的?
下午,曾经告诉我,测试应该用这样一种方式,从街上走来的人,应该能够运行它们。我的意思是这是不可能的,但需要时间,很多时间。必须找到一种方式来解释的概念并不是真的在每天字典(例如API)。

我认为他们希望somenthing这样的当测试步骤很清楚——YouTube 16

你怎么认为?你怎么做?

I want to ask a question that is both simple and complex to answer: How do you write your test cases?<\/p>

Why do I say it is simple?<\/p>

Well I mean according to some definitions testers write test cases and since they do it often it should be easy. Also there is a ton of information online on how to write a test case, what should it contain, so again, easy and simple.<\/p>

Why do I say it is complex?
Well, a PM once told me that the tests should be written in such a way that a person coming from the street should be able to run them. I mean that is not impossible to do but it will take time, a lot of time. One has to find a way to explain concepts that are not really in the day to day dictionary ( API for example).<\/p>

I think that they want somenthing like this\u00a0When tests steps are really clear - YouTube\u00a016<\/a><\/p>

What do you think? How do you do it?<\/p>","quoteUsername":"IOan","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

2回答

一个
Userlevel 5
徽章 + 3

在旧的日子,我曾在任何敏捷项目(这里显示我的年龄,我知道:cP),我们使用需求,理解和讨论他们最好的,我们可以创建一个技术规范文档(文件,说这是一个草案屏幕布局你会得到+每个选项可能会做些什么),那么涉众可能不会玩这个应用程序在一个α/β/ UAT测试阶段结束时几乎发展…那些日子没有频繁冲刺演示。

当以后工作在一个测试经理、测试人员或UAT协调人的角色,我倾向于构建测试用例基于同一背景…,用户将“从大街上”,不可能看到的应用程序,无论他们是5岁或者95岁,可以按以下步骤完成。

我尝试过“反模式”的方法是对细节的这些在这样一个狭窄的方式像“点击蓝色按钮在屏幕的右上角“登录。我不再这样做从GUI变化经常经历+需要更新的步骤,所以1警告我可以建议将有一个细线添加细节足以让任何新的能够遵循步骤,或过分,搞砸了测试用例维护…“单击登录按钮”可能比前者更好的例子在我看来现在…

In the days of old, before I worked in any agile project (showing my age here, I know :cP), we used to take requirements, understand them & discuss them the best we could, create a technical specification document (file that says this is a draft screen layout you\u2019re going to get + what each option might do), then the stakeholders might not get to play with the app before an alpha\/beta\/UAT testing phase almost at the end of the development\u2026\u00a0in those days there were no frequent sprint demos.\u00a0<\/p>

\u00a0<\/p>

When later working in a test manager, tester or UAT co-ordinator role, I tend to build test cases based on the same background\u2026\u00a0that the users would be \u201coff the street\u201d, never perhaps having seen the application and whether they are 5 years old, or 95 years old, could be able to follow the steps through to completion.<\/p>

\u00a0<\/p>

One \u201canti-pattern\u201d approach I tried was to detail these in such a narrow way like \u201cclick the blue login button in the top right of the screen\u201d. I stopped doing that from experiencing the GUI changing so often + needing to update the steps, so 1 caveat I could advise on would be there is a fine line adding detail enough for anyone new to be able to follow the step, or going overboard to screw up test case maintenance\u2026\u00a0\u201cclick the login button\u201d is probably a lot better than the former example in my opinion now...<\/p>","quoteUsername":"alex_read","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

年代
Userlevel 4
徽章 + 4

大约36年前,在1987年May21st,我写了我的第一个测试用例是测试人员。在那一天我写了12人。但是在大多数情况下,作为一个测试人员,我不“写测试用例。“这是更准确的说我设计和执行测试。有时我做,结果你会点,说“嘿,看起来像一个测试用例”和其他许多次它不。主要是没有。

我最喜欢的事情是编写工具,生成大量数据,然后我样本数据驱动高度探索性调查的产品。

为我现在的客户,我一直帮助复制一个难以捉摸的数据丢失。这包括执行成千上万的重复动作,即使某些随机变化。这是一个测试用例吗?成千上万的吗?嗯,我称它为一个测试活动。

当我教测试时,我几乎不谈论测试用例。我不是说这是一个坏的或无用的概念,提醒你。我只是说我不明白为什么是这样一个流行的想法在测试人员…除非国税局仅仅因为他们不知道还有什么可说的。

Almost 36 years ago, on May21st 1987, I wrote my first ever test cases as a paid tester. On that day I wrote 12 of them. But for the most part, as a tester, I don\u2019t \u201cwrite test cases.\u201d It\u2019s more accurate to say that I design and perform tests. Sometimes I do that in a way that results in something you would point at and say \u201chey, that looks like a test case\u201d and many other times it does not. Mostly not.<\/p>

My favorite thing is to write tools that generate a lot of data, and then I sample that data to drive highly exploratory investigations of the product.\u00a0<\/p>

For my current client, I\u2019ve been helping to reproduce an elusive data loss bug. This has involved performing thousands of repetitive actions with certain random and non-random variations. Is that one test case? Is it thousands? Well, I call it a test activity.<\/p>

When I teach testing, I barely talk about test cases. I\u2019m not saying it\u2019s a bad or useless concept, mind you. I\u2019m just saying I don\u2019t get why it\u2019s such a popular idea among testers\u2026\u00a0unless irs just because they don\u2019t know what else to talk about.<\/p>","quoteUsername":"satisfice","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

回复


ShiftSync条款和条件
Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">

金宝搏app官网下载
Baidu
map