Scenario: For verifying the pagination links: First page     # features/project/project_search.feature:113
    And I should see the following <links>                     # FeatureContext::iShouldSeeTheFollowingLinks()
      | links |
      | next  |
      | last  |
      | 1     |
      | 2     |
      The link '1' was not found
    And I should not see the link "first"  

It looks like the exception text could be more descriptive, too although I'm not sure about that - seems like all the links weren't found.

Comments

sachin2dhoni’s picture

Status: Active » Needs review

When I run this feature for the first time it got timed out and when i ran the feature for 3 times i did not get any time out ! and i could see all passed cases as well.

Modified the feature file with minor change for better redability.

Please check the commit log:
d2f5460

eliza411’s picture

Status: Needs review » Needs work

This still fails for me with no timeouts.

 Scenario: For verifying the pagination links: First page     # features/project/project_search.feature:113
    And I should see the following <links>                     # FeatureContext::iShouldSeeTheFollowingLinks()
      | links |
      | next  |
      | last  |
      | 1     |
      | 2     |
    And I should not see the link "first"                      # FeatureContext::iShouldNotSeeTheLink()
      The link first was present on http://git6site.devdrupal.org/project/issues and was not supposed to be.
sachin2dhoni’s picture

Status: Needs work » Needs review

Updated to the dev branch with the fixes.

Please check the commit log: ce9cee5

sachin2dhoni’s picture

Issue tags: +sprint 8

Tagging

eliza411’s picture

Component: Failing test » Step definitions

Looks ready for code review.

If jhedstrom doesn't have any ideas about what to do with the .htaccess reauth this page causes, we should assign this to sdboyer and ensure that the @ci tests will be allowed access to the test site by IP address, maybe. It should also be tagged in a meaningful way so that if the tests continue to require manual auth for .htaccess they can be easily excluded.

eliza411’s picture

Assigned: Unassigned » sdboyer

Assigning to sdboyer for feedback

sachin2dhoni’s picture

 @javascript @wip @known_git6failure
 Scenario: When Searching for the Project title              # features\drupalorg\project_search.feature:27
   When I fill in "Project" with "Achie"                     # FeatureContext::fillField()
   And I select "Achievements" from the suggestion "Project" # FeatureContext::iSelectFromTheSuggestion()
   And I press search to filter                              # FeatureContext::iPressSearchToFilter()
   Then I should see at least "5" records                    # FeatureContext::iShouldSeeAtLeastRecords()
   And I wait for "1" seconds                                # FeatureContext::iWaitForSeconds()
   And I should see "Achievements" under "Project"           # FeatureContext::iShouldSeeUnder()
     The text 'achievements' was not found in all the rows of the column 'Project'
sachin2dhoni’s picture

The issue mentioned in comment #9 is due to running the old copy of the feature.
I have updated the latest file in the path drupalorg/project_search.feature instead of placing it "project/".So I have moved the updated file under "project/".

Please check the commit log:017e31b

eliza411’s picture

Assigned: sdboyer » Unassigned

I still get failure on step 22 because of the prompt for .htaccess. I tagged that scenario, and sdboyer has whitelisted the CI server. We can choose to run these tests or not based on the tag, and I'll be testing later today whether they're successful as they should be from the bddtest server.

eliza411’s picture

Title: project/project_search.feature is failing » project_search.feature is failing

updating title

sachin2dhoni’s picture

Title: project_search.feature is failing » project_search.feature is failing(issues_search.feature)
eliza411’s picture

Title: project_search.feature is failing(issues_search.feature) » issues_search.feature is failing
Status: Needs review » Needs work

project_search is now issue_search, is that correct? I've update the title accordingly. If I'm wrong, lets make sure this issue is about just one test :)

sachin2dhoni’s picture

Status: Needs work » Needs review

Yes it is issues_search instead of issue_search.

Please check the commit log for reference.

http://drupalcode.org/project/doobie.git/commit/b7e28fa

sachin2dhoni’s picture

Version: » 6.x-1.x-dev
Issue tags: +sprint 10

Tagging

eliza411’s picture

Status: Needs review » Reviewed & tested by the community

Looks good. I double checked that all scenarios affected by .htaccess are marked.

kssundar’s picture

Version: 6.x-1.x-dev » 7.x-1.x-dev
Component: Step definitions » Test needs update
Assigned: Unassigned » kssundar
Status: Reviewed & tested by the community » Patch (to be ported)
Issue tags: +sprint 18

Need 7.x update

kssundar’s picture

Status: Patch (to be ported) » Needs review
eliza411’s picture

Status: Needs review » Reviewed & tested by the community

This is as good as we can get this until D7 Drupal.org is ready for feedback.

I've removed the @htaccess tag since git7 is no longer reprompting for authentication.

eliza411’s picture

Status: Reviewed & tested by the community » Closed (fixed)
eliza411’s picture

Issue summary: View changes

.