使用 Scenario Outlines 和 Ruby 验证不同字段中的消息

Question

I have a big problem: with all invalid Login messages appearing in a single field, I can validate it by doing this: I'm going to map the only element where the message's invalid alert appears and use expect to validate the Scenario Outlines message X the message extracted from the element's text.

msg_invalid = screen_login.msg_erro_login.text
  expect(msg_invalid).to eql(msgs)

  
   What if the messages appear in different fields like the attached image?

       
        Given that the user is on the login page
        When providing incorrect email "<email_login>" or password "<pswd_login>"
        Then he can see the alert message "<msgs>"

Examples:
        | email_login             |  pswd_login   |     msgs                   | 
        |                         |               | This is a required field.  | 
        |staulik@b2card.com       |               | This is a required field.  | 
        |                         | test123       | This is a required field.  | 
        |staulikb2card.com        |               | Please enter a valid email address (Ex: johndoe@domain.com). 

|

Answer 1

TL;DR

Since the source for your HTML, CSS, JavaScript, and model/controller weren't provided, it's hard to guess what your real problem is. However, you've given enough information to suggest that you're going about this particular set of tests sub-optimally, and would be better off refactoring the tests or modifying either the login implementation or the user interface to be more testable.

NB: This is a good example of why test-first development is useful. Retrofitting tests onto existing code is harder than making sure the testability is baked in from the beginning!

What to Validate and Where to Validate It

This isn't really a Cucumber outline problem. The issue is most likely with the steps of your test, or underlying UI issues. There's a strong likelihood that you either aren't using unique CSS ID's or other consistent and easy-to-locate information related to your flash messages if the validation is being done server-side, or that you aren't properly driving the web page if you're doing validation in JavaScript and manipulating the DOM to insert your error messages.

Furthermore, the UI itself isn't the ideal place to test anything other than valid or invalid logins. If you want to know why a login is invalid, for security reasons you generally want to do the more granular testing in the model or controller tests if you want to know why a given login failed. You should never return things like "incorrect password" or "invalid username" (as opposed to "invalid login") that leaks information about whether a given account even exists.

Additionally, email validation is generally a waste of time. While there are some very complex regular expressions that come close—see this Perl regex for RFC 822 addresses as an example—email addressing was never designed to conform to regular expression patterns. Furthermore, most people implement email validations badly, and naive validations often won't accept perfectly valid email addresses such as plus-addressing or qmail-style dash extensions. Additionally, even putting in a "valid" email address that matches RFC 822, RFC 5822, or whatever RFC you're trying to validate against can't actually validate that it's a deliverable email anyway.

Given the above, you should most likely just validate that both fields are non-empty before allowing the Sign-In button to be clickable. That seems to be the main check you want to do anyway. Otherwise, just check the page for some invariant "invalid login" text provided by the flash or whatever you're using to manipulate the DOM during text entry or when validating logins.