问题

断言

  • 2023年5月2日
  • 3回复
  • 52岁的观点
IOan
Userlevel 4
徽章 + 3
  • IOan
  • 0.8跨声速
  • 6个回答

你把你的断言在自动化代码?

\u00a0<\/p>

\u00a0<\/p>","quoteUsername":"IOan","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

3回复

Shabareesh莲花
Userlevel 1
徽章

我致力于硒时,下面我用断言类别。

  • 断言=
  • 维护布尔
Shabareesh莲花
When I was working on Selenium, I have used below Assert categories.\u00a0<\/p>
  • Assert Equals<\/li>\t
  • Assert Boolean<\/li><\/ul>","quoteUsername":"Shabareesh Padma","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">
年代
Userlevel 4
徽章 + 4

我不使用断言。

相反,我通常写代码,生成的数据,用于产品的自动检测。

然后我编写代码,数据适用于该产品。当我做gui级工作,我有时使用一个页面对象的设计。我对产品如何收集数据的行为并保存它。我不觉得它有助于把大量的断言代码,因为我通常使用GUI为我创造一个稳定的回归检查(因此低级断言几乎从不失败,检查我所能做的一切在一个更高的水平)。同时,断言测试逻辑,我喜欢单独的测试逻辑与逻辑操作产品。

作为一个单独的进程,我编写代码来分析数据和旗帜有趣的事情。这需要通过和失败的形式时,我把整个过程叫做“检查。“当需要警报和可视化的形式,我把它叫做“萎靡不振的。“我喜欢关注复杂的神谕,而不是简单的断言。

一个问题我有漏网的策略断言代码是每个人谁似乎忘记它们是什么或不检查。你有无数断言…它等于什么?通过编写专用的程序作为神谕,我发现我还能有效跟踪。

需要注意的另一件事是,我写我自己的框架,而不是使用PyTest或之类的。

I don\u2019t use assertions, as such.<\/p>

Instead, I usually write code that generates data for use in an automated assay of the product.<\/p>

Then I write code that applies that data to the product. When I\u2019m doing GUI-level work, I sometimes use\u00a0a page-object design.\u00a0I collect data about how the product behaves and save it. I don\u2019t find it helpful to put a lot of asserts into that code because I\u2019m usually working with a stable GUI for which I\u2019m creating regression checks (thus\u00a0low-level asserts would almost never fail, and all that same checking I can do on a higher level anyway). Also, asserts are testing logic, and I like to separate testing logic from logic that operates the product.<\/p>

As a separate process, I write code to analyze that data and flag interesting things about it. When this takes the form of pass and fail, I call the whole process \u201cchecking.\u201d When it takes the form of alerts and visualizations, I call it \u201cflagging.\u201d I like to focus on complex oracles rather than simple assertions.<\/p>

One problem I have with the strategy of peppering code with asserts is that everyone who does that seems to lose track of what they are or are not checking. You have a zillion asserts\u2026\u00a0what does it amount to? By writing dedicated programs to serve as oracles, I find I can keep better track of that.<\/p>

Another thing to note is that I write my own frameworks, instead of using PyTest or that sort of thing.<\/p>","quoteUsername":"satisfice","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

一个
Userlevel 5
徽章 + 3

总是在测试用例或测试步骤。这地方正好在个人项目的要求责任&使最大限度地重用、共享的理解+清晰的(工作方式的期望断言)然后易于维护。

  • POM水平:
    • projectA Application123 LoginPage POM的添加一个方法,声称提交凭证导致一个成功的登录和仪表板页面显示“欢迎,用户名”显示。
    • projectA然后需要添加负面测试用例,POM方法需要一个条件分支或复制方法扭转断言
    • ProjectB和另一个团队想要与同一Application123从他们的项目。他们的验证标准检查页面的外观和感觉,仪表板页面显示该公司标志在正确的地方,字体样式和背景颜色是按预期(他们不关心欢迎,用户名”文本)
  • 测试自动化框架:可以是相同的
  • 辅助方法:取决于他们位于——测试用例,测试数据,POM,报告或其他?在我看来测试用例和测试步骤辅助方法工作断言,其他地方没有

在上面的例子中,设计一个LoginPage POM等方法isIncorrectLoginMessageShown (), getTextofIncorrectLoginMessage (), isUserNameEmpty (), isSubmitDisplayed(),然后DashboardPage POM等方法isPageDisplayedAndLoaded (), getWelcomeText()等将支持更多的项目和给他们每一个的责任决定什么是根据自己的需求通过或失败的标准。

Always in the test cases or test steps. This places it squarely at the individual project\u2019s requirement responsibility & enables maximum reuse, shared understanding + clarity (ways of working of where to expect the assertions) then ease of maintenance.\u00a0<\/p>

\u00a0<\/p>

  • POM level:<\/strong>\u00a0\t
    • projectA adds a method to Application123\u2019s\u00a0LoginPage POM, which asserts that submitted credentials result in a successful login and the dashboard page then showing with \u201cwelcome, UserName\u201d shown.<\/li>\t\t
    • projectA then needs to add negative test cases, either the POM method now needs a conditional branch or a duplicated method reversing the assertion<\/li>\t\t
    • ProjectB with another team wants to interact with the same Application123 from their project. Their validation criteria is to check the look & feel of the page - the dashboard page displays the company logo in the right place, the font style & background colours are as expected (they don\u2019t care about the welcome, UserName\u201d text)<\/li>\t<\/ul><\/li>\t
    • Test Automation Framework:<\/strong> can be the same<\/li>\t
    • Helper methods:<\/strong> depend on where they\u2019re located - are they test case, test data, POM, reporting or other? In my view test case & test step helper methods work to have assertions, other places not<\/li><\/ul>

      \u00a0<\/p>

      In the above example, designing a LoginPage POM with methods such as isIncorrectLoginMessageShown(), getTextofIncorrectLoginMessage(), isUserNameEmpty(), isSubmitDisplayed(), then a DashboardPage POM with methods such as isPageDisplayedAndLoaded(), getWelcomeText() etc. will support more projects & give them each the responsibility of deciding what is a pass or failure criteria depending upon their own requirements.<\/p>","quoteUsername":"alex_read","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

回复


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