A few thoughts.

First, this test violates the separation of concerns between the page object model (cfme_pages), and the pages tests (cfme_tests). A good rule of thumb is that tests (in either suite) should never call out to selenium methods. Page objects themselves should abstract selenium away from the test caller. In this case, find_element_by_xpath, as well as the following use of the 'text' property, should be done on the AboutPage object in the cfme_pages project.

Here's what I would expect this test to look like with an augmented About page:
```python
    def test_version(self, cnf_about_pg, basic_info):
        '''Tests version number against one present in cfme_data yaml'''
        Assert.contains(
            basic_info['app_version'], cnf_about_pg.version_number,
            "Major version number should match")
```

Second, following-sibling XPath is sometimes slow for no reason. It might be easier and faster to pull all the `td` elements and sort through them in python.

Third, we should be able to trust the cnf_about_pg fixture to do its job. We have an established convention of Asserting `is_the_current_page` on fixtures, but that seems noisy to me. Probably we should enhance the fixtures to handle that assert...I'll open an enhancement for that.

Finally, if we're only interested in the major version, as the message would indicate, it might make sense to expose the version parts as a tuple (or other suitable sequence type) on the AboutPage model for easily breaking it down into components an comparing them individually.