Closed (fixed)
Project:
Drupal.org BDD
Component:
Step definitions
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
31 Jul 2012 at 17:37 UTC
Updated:
4 Jan 2014 at 02:24 UTC
Jump to comment: Most recent
This may overlap with some other tests, but in this case we should be checking that a newly create sandbox, sandbox that has been promoted to a project, and project are all appearing properly
Project tab - Project tab should NOT appear for anyone but the auth user
Project tab - Project tab should appear for the user
Commit numbers - Verify commit numbers are lower than in d.o.
Project list - Sandbox project should appear
Projects links - Project links lead to the main project page
SSH Keys tab - Verify tab exists
Comments
Comment #1
pradeeprkara commentedtagging for sprint 3
Comment #2
sachin2dhoni commentedComment #3
sachin2dhoni commentedPage considered: http://drupal.org/user (After login)
I have a few questions as below:
Project tab - Project tab should NOT appear for anyone but the auth user
[Suresh]: We assume "Project" is not a tab but a heading/section below the page.
Commit numbers - Verify comment numbers are lower than in d.o.
[Suresh]: Currently when i login as 'site user' or 'git user' or other users, i do not find any data for "Projects". We created a project as 'site user' but were not successful in creating a repository. We followed the instructions from here - http://git6site.devdrupal.org/project/1668843/git-instructions and are getting "Permission denied" message when we try to push or pull.
Please provide us an account that has commits done or help us create a project/repo so that we can do some commits and we will be able to see the commit numbers on the profile page.
Project list - Sandbox project should appear
Projects links - Project links lead to the main project page
[Suresh]: Depends on the above point.
Comment #4
eliza411 commentedThe only help available until I am back (for creating repos) is in the features/git/repo.feature file and its steps and it's not solidly implemented.
Site user should NOT be able to create a project (has not agreed to terms of service)
Check that git user has agreed to terms and that git vetted has as well. They should be able to push.
Feel free to postpone this issue until the next sprint as creating repos isn't easy.
Comment #5
kssundar commentedTo test items 3, 4 and 5, we need either of the below two:
1. a project and git repository should be created by 'git user'
2. A user credentials who has already created a project, repo and has done some commits
If its difficult to create a project and repo, then we can go for option 2.
Please suggest.
Comment #5.0
kssundar commentedclarifying need for creation of new data
Comment #6
eliza411 commentedI'm going to assign this to me to get set up as there are a lot of sticky git creation issues that I need to look into. I'll assign it back when I can give you enough information to work with.
Comment #7
pradeeprkara commentedtagging for sprint 4
Comment #8
eliza411 commentedWe have all the git things worked out in repos.feature (or as close as we're likely to get for a while), so I'm assigning this back.
Comment #9
kssundar commentedTaking this one and plan is as below;
The scenarios will:
1. create a project
2. create repository
3. do a couple of commits
4. verify commit numbers and project titles in profile page
Please correct me if there needs to be any change.
Comment #10
kssundar commented"Pushing to repo" step is committed here which needs review - #1743082: Verify Maintainers tab and its permissions (project_maintainers_tab.feature, edit, vcs, maintainers, issues, releases)
Comment #11
eliza411 commentedThe plan looks solid to me. #1743082: Verify Maintainers tab and its permissions (project_maintainers_tab.feature, edit, vcs, maintainers, issues, releases) needs to delete the repo it creates when it is done, but that's already noted over there.
Comment #12
kssundar commentedtagging
Comment #13
kssundar commentedFeature created and committed - http://drupalcode.org/project/doobie.git/commit/82f1d25
Comment #14
eliza411 commentedSimilar feedback on given/when/then to http://drupal.org/node/1706768#comment-6449432
Comment #15
kssundar commentedUpdated feature and step definitinos according to the suggestions.
http://drupalcode.org/project/doobie.git/commit/80e72ef
Comment #16
eliza411 commentedLooks good to me, moving forward for code review.
A note about dependent scenarios: As far as tizzo and I have been able to work out, we're stuck with dependent scenarios within a feature file; let's continue to tag them as such but as long as they don't cross into dependencies on other feature files, we should be okay.
Comment #17
jhedstromCode changes look good.
Comment #18
eliza411 commentedmerged to master
Comment #19.0
(not verified) commentededited Commit numbers - Verify comment numbers are lower than in d.o. to Commit numbers - Verify commit numbers are lower than in d.o.