beta.drupal.org is ready to QA!

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
lisarex's picture

The redesign of the drupal.org site is nearing completion, and we’re looking for people to help us Quality Assurance (QA) test beta.drupal.org to identify problems with functionality and visual implementation before launch. There should be opportunities for people of all skills to help us identify or fix problems.

Bill O'Connor (csevb10) is leading the QA effort and can be reached on #drupal-redesign on IRC or in the issue queues.

We need help with the following two tasks: Functional Testing and Cross-browser testing.

Note: if you discover a problem outside of the issue you're working on, check for an existing issue before filing a new QA issue. Instructions for filing a new issue are Task 3 below.

Task 1: Functional QA Testing all items tagged as drupal.org redesign qa

  1. Choose an issue from the queue that isn't assigned to someone else (w/out [Theme] appended): http://drupal.org/project/issues/search/redesign?issue_tags=drupal.org+r...
  2. Assign it to yourself
  3. Go to http://beta.drupal.org (user name and password are drupal/drupal)
  4. Ensure that the feature works (aka does what it should)
  5. Ensure that it behaves logically: if what it does technically works, but it doesn’t make sense, it may need to be fixed.
  6. Log any problems in the issue. Include:
  • what is expected - aka how you would expect it to behave
  • what it does - aka how it is wrong
  • steps to recreate - aka what do we need to do in order to see the problem in action
  • attach a screenshot (if possible) to show the error in action
  • add the tag ‘drupal.org redesign qa code’, in addition to the existing tags.

Task 2: Functional cross-browser testing all items tagged as drupal.org redesign qa:

  1. Choose an issue from the queue that isn't assigned to someone else (w/ [Theme] appended): http://drupal.org/project/issues/search/redesign?issue_tags=drupal.org+r...
  2. Assign it to yourself
  3. Review https://infrastructure.drupal.org/drupal.org-style-guide to get a sense for what the designs should embody.
  4. Test for visual blemishes, e.g. major alignment problems (e.g. no need to report something that doesn’t match the prototype exactly) in these browsers (Please note the browsers tested in the issue):
  • IE7+
  • FF3+
  • Safari
  • Chrome
  • Log any problems in the issue. Include:
    • browser (e.g. ie7, or ‘all’)
    • what is wrong with the theming now
    • what should the theming should be
    • screenshot of the theming issue
    • add the tag ‘drupal.org redesign qa theme’, in addition to the existing tags.

    Task 3: Filing a new issue (only if you discover a new issue not already discussed in the Redesign queue)

    1. Go to The Redesign project.
    2. Prefix new issues with "QA:"
    3. Component = choose one
    4. Category = "bug report"
    5. Tags = 'drupal.org redesign', 'drupal.org redesign qa' and either 'drupal.org redesign qa theme' or 'drupal.org redesign qa code'

    Comments

    In case of success...

    marcvangend's picture

    Any instructions in case I don't find any errors?

    Good question!

    lisarex's picture

    If you don't find any problems on a QA issue, mark it as 'reviewed & tested by the community' with a comment with any other details, and then csevb10, Drumm, dww, myself etc will review again and mark it as fixed.

    ==================================
    http://about.me/lisarex

    looking good

    madjr's picture

    the new design is really nice

    i see that we now have bookmarks on user page http://beta.drupal.org/user

    any chance that bookmarking can be extended to more than forum posts?

    like modules and themes?

    that would reduce a lot the constant need for repeated searches and probably help the server load and speed a bit :)

    also, is the new site in drupal6 or 7?

    Thanks madjr! If you have any

    lisarex's picture

    Thanks madjr! If you have any suggestions, feel free to create them as issues (unless the issue already exists). We won't be adding any new features for awhile though. The site is in Drupal 6, and will be upgraded to 7 at some point after Drupal 7 is released.

    ==================================
    http://about.me/lisarex

    How to collate issues?

    dipen chaudhary's picture

    Spent couple of hrs on the issue queue and reported some 7-8 issues sometimes on the issue that are not assigned to me, since everyone is reporting on every issue they feel is broken (which is awesome) there needs to be a collated list of problems with an issue? Or thats the job of the QA team? I think it will also be nice if reporters include what tests/use cases they run QA tests for.


    Dipen Chaudhary
    Founder, QED42 http://www.qed42.com Drupal development

    I just want to avoid creating

    dstol's picture

    I just want to avoid creating more work for everyone.

    If I only want to do QA, do I still mark it as rtbc (if it is) or is it rtbc after both QA and cross browser?

    I'll QA issues all day, just so long as I'm doing it right. http://drupal.org/node/935356

    From IRC

    dipen chaudhary's picture

    I had a similar question, so copying here:

    (12:26:22 IST) dipen: csevb10: if I find a functional glitch, should i create a new issue for it or just update the same issue?
    (12:27:35 IST) csevb10: dipen: feel free to just update the issue
    (12:27:46 IST) juaneclark [~Adium@c-67-177-199-233.hsd1.co.comcast.net] entered the room.
    (12:28:01 IST) csevb10: dipen: and fill in as many items as needed. when we've cleaned all of the issues for that area, we'll close the ticket
    (12:28:25 IST) csevb10: dipen: if something is particularly large, we can open new tickets, but I want to make sure things stay manageable
    (12:28:48 IST) dipen: csevb10: alright, should i change the category from task -> bug or do any changes on the metadata of the issue? should it be assigned to someone or should be assigned to myself?
    (12:30:15 IST) dipen: csevb10: basically I will let issues setting be the same or should i update them? Coz I am not sure if I should change the category from task to bug or whatever.
    (12:30:20 IST) kjay left the room (quit: Quit: kjay).
    (12:30:40 IST) dipen: csevb10: I think I will just let it be for now and just put in my comments..
    (12:30:42 IST) csevb10: dipen: you can leave as task, but mark as "needs work"

    Every component has a QA issue and Theme issue, issues which are suffixed with [Theme] in the title are theme issues and if not then functional. For either, if you think that its not done properly, then mark it as "needs work" and if you think its a go then mark it as "reviewed and tested by community" after which someone from QA team will do a final review and close.

    Makes sense?


    Dipen Chaudhary
    Founder, QED42 http://www.qed42.com Drupal development

    For QA

    subadmin's picture

    i offered himself for Quality Assurance and i will be testing.

    This is amazing

    mindtrades's picture

    The beta looks and functionality are awesome, Would contribute in QA testing.

    The Front page is mess and completely useless

    Daniel J Wilcox - Blocked for personal attacks's picture

    At least with the current design you can see some blog and forum posts on the front page

    The new design is is just a visual mess and you cant take anything in

    Its the one of the worst Drupal designs i have ever seen, it just reinforces the notion that Drupal sites are big ugly and clunky

    Its looks like no one on the team has ever built a Web site, has any design experience or knows anything about content management

    You should all hang your heads in shame for creating something so amateurish and hideous looking

    Which issue did you check?

    yoroy's picture

    Which issue did you check? Thanks for contributing!

    Which issue did you check?

    pljordaan's picture

    Yesterday I posted here for a bug in a translation nl.po file for Drupal 7 Beta 1, because I taught Q&A was question and answer, when I discovered this I removed the post! See below. I posted it again in a forum. This site is rather confusing.

    Sorry,

    Peter

    =====================================================================

    Comment 'SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'na' by pljordaan

    Sorry,

    I taught Q&A stood for Questions & Answers, so I removed the content!

    Peter

    View original: http://groups.drupal.org/node/97729#comment-313579
    Post a reply: http://groups.drupal.org/comment/reply/97729/313579

    --
    This is an automatic message from groups.drupal.org To manage your subscriptions, browse to http://groups.drupal.org/user/258159/notifications
    You can unsubscribe at http://groups.drupal.org/notifications/unsubscribe/sid/825604?signature=...

    First Time User Feedback

    nicelobster's picture

    I made some notes on skitch. Basically, the "get started" page has some stuff in it that's confusing. The numbered step design suggests that it's a step through process. When I click on "Extend", I got disoriented that the steps at the top disappeared and that it landed me on a page w/a different title (download & extend). Not a huge deal, but these details matter.

    What about re-ordering the top nav to mirror those steps?

    Only local images are allowed.

    This is very good specific

    laura s's picture

    This is very good specific feedback that explains the why behind your suggestion. Thank you! Did you create an issue to put it into consideration?

    Laura Scott
    PINGV | Strategy • Design • Drupal Development

    not yet

    nicelobster's picture

    Hey Laura, I didn't. Can you tell me more how that works as far as who can submit etc... protocol?

    Hi Nica :) Thanks for the

    lisarex's picture

    Hi Nica :)
    Thanks for the screenshot. You can post to the Redesign project (link in the main post). We'll review all suggestions, will also be usability testing with non-Drupal community members and will look for patterns. The feedback may or may not make it into the initial release but we want to hear concrete, actionable ways the existing design can be improved (and your screenshots does that).

    ==================================
    http://about.me/lisarex

    Good feedback

    Wolfflow's picture

    Wonder at,
    looking for the 10th time I did not notice this, instead just clicking around (to proud to admit myself I was just confused) ....

    Solution

    nicelobster's picture

    This could also be solved by reomving the links for steps 1-4. I talked to Neil about this and he said that they weren't links in the comps.

    I'm curious how to help in

    Kirk's picture

    I'm curious how to help in terms of general thoughts?

    As a whole, I like the look that the team is attempting to go for, it is very modern and the sort of thing I expect to see on a FOSS project the size of Drupal.

    What I am concerned about, however, is that I think the new design (as it currently stands) is very difficult to follow and dare I say "overwhelming" to a novice user. I don't see any specific places in the issue queue to address such concerns and would like to provide feedback as much as I can.

    I'd love to get us all in a

    lisarex's picture

    I'd love to get us all in a big room with a whiteboard to discuss :) Sadly, that's not possible.

    If you can describe what you feel is overwhelming in an issue, with an annotated screenshot (like Nica's done above) in the Redesign project queue (instructions are in Task 3 above), that would be helpful. We are reviewing all feedback.

    ==================================
    http://about.me/lisarex

    Sounds good Lisa. There are a

    Kirk's picture

    Sounds good Lisa. There are a few things that immediately spring to mind, that I think could probably be easily fixed. I'll put together some screenshots for you shortly.

    Just wanted to make sure I was posting this sort of stuff in the correct place before I jumped in.

    Footer concerns

    nicelobster's picture

    Only local images are allowed.

    This may not get fixed for launch, but perhaps we can reconsider sandwiching downloading Core and other things. From an outside standpoint, I would intuitively think in these terms:

    1. Download Drupal
    2. Add Crap on to it.

    We should organize it as such...

    Typography Edit

    nicelobster's picture

    Only local images are allowed.

    Hi Nica, thanks for these,

    lisarex's picture

    Hi Nica, thanks for these, but these definitely need to be posted as issues to the Redesign project so the team can comment / take action. Instructions are in Task 3 in the main post.

    ==================================
    http://about.me/lisarex

    Just helped out with an issue

    Wolfflow's picture

    Hi Lisarex, dunno if it's Ok, but I made an issue : http://drupal.org/node/939998 for First Time User Feedback post.

    I miss having several case

    jazzdrive3's picture

    I miss having several case studies, along with the teasers, on the front page. I understand why it's now done like that, and taking away the full list.

    But even if remains only showing one case study, having the teaser on it would be a good thing. Draw people in to the story as opposed to just an image.

    Redesign Drupal site

    ecommercium's picture

    Hi, Just a note. The redesign looks great and works great! I just can't wait having it gone live! Great job you all guys done (and do!) at the redesign team!
    Marco - UX designer, Netherlands

    It's really great , tnx for

    shima's picture

    It's really great , tnx for your try ;)
    just i hope it had some dynamic effect & animation like menu ore tabs or slide something that show it life :D

    Redsign Drupal

    subadmin's picture

    It is great effort from Drupal Team.
    theming is now better.

    Back to the old version!

    ggd's picture

    Dear colleagues,
    how can I switch the interface to the old version?
    The new design is rather difficult to read. Fonts are awful!
    I'll not discuss the other aspects of usability. Let me use the nice old site!
    Could you include in drupal.org some modules to make user's custom settings for page views?

    Second the ability to return to the old layout

    greywolfsspirit's picture

    I know my way around the old setup a lot faster having used it for so long now. This new interface is not as 'straight forward and to the point' like we are used to having. If it's merely a Theme thing, allow us to switch back to the old theme/layout if we don't like the new one.

    Grumble grumble

    rfay's picture

    We'll all get used to this, and a lot will be better and we'll miss some of it. This is a normal part of any change like this.

    There's just no way that we have the community resources to maintain two separate themes (and design concepts) so we're not going to provide both themes. Lots of features of the redesign won't work on the old theme, and there's lots of new module code in the redesign.

    Let's get used to it. If you have particular problems, file issues against them. Better yet, create a patch that makes it better.

    Guys, why not give the new design a chance?

    mynameispj's picture

    You know your way around the old set up simply because you used it for so long. The new design has been live for, what, a day? Why not try to actually give it a chance?

    My opinion, as a designer, is that the new site absolutely destroys the old one. Its easier, its more intuitive, its more usable, and its set up in a way that makes getting acquainted with Drupal a much easier process for people who are investigating it but aren't as familiar with it as the rest of you.

    Plus, as a branding move, it's fantastic, and already working wonders. I have colleagues who use Wordpress and ExpressionEngine, who used to laugh at my insistance to use Drupal, telling me they're going to give Drupal another chance, simply after seeing the redesigned site. The new design lends the CMS's brand some much needed aesthetic respectability.

    Yes, you have to spend a little bit of time and effort becoming reacquainted with how things are set up now, but that's not an indication of which design is better, only which one you've used longer. Plus, if I understand correctly, the redesign process was conducted largely a community effort, where people had the opportunity to give feedback--so why are you guys upset now?

    Give the new design a shot, and give the folks who worked so hard to do such great work some much-deserved kudos. It really is a remarkable amount of work that the redesign team did, and I think they have every reason to be proud.

    Back!

    ggd's picture

    Very nice tradition to avoid the direct answer.
    @Rfay advises to wrote issues and pathces.
    @mynameispj looks for a chance.
    I have not asked about it. The both are not able to answer my question.

    How can I switch the interface to the old version?

    P.S. If you are not able to maintain two themes then I could.

    I'm pretty sure Rfay did

    mynameispj's picture

    I'm pretty sure Rfay did answer your question. You can't switch back to the old version.

    Usability

    ggd's picture

    Well. Could you at least replace the awful fonts to readable ones?

    Are you on Windows

    BrightBold's picture

    @gdd - are you viewing the site on a Windows machine? There was a problem with an older version of Lucida Sans on Windows that made it display really terribly, and I'm wondering if this is what you're seeing. It would be helpful if you could create an issue saying you find the fonts unreadable, indicate your operating system, and provide a screenshot.

    That would enable the redesign team to decide whether the font stack needs to be tweaked.

    There are people working on

    lisarex's picture

    Yep, we know about this... there are people working on the font issues right now.

    ==================================
    http://about.me/lisarex

    No one is avoiding anything

    Darko's picture

    @rfay answered your question directly:

    There's just no way that we have the community resources to maintain two separate themes (and design concepts) so we're not going to provide both themes. Lots of features of the redesign won't work on the old theme, and there's lots of new module code in the redesign.

    I like a lot about the new

    NathanM's picture

    I like a lot about the new site design. However, the font/typography situation could be improved upon. For some reason, fonts look squished and pixelated on the new site, almost as if I'm viewing the text zoomed out on my iphone. Looking at the comments, I wasn't the only person who noticed this. Other than that, I think it is mostly a positive improvement.

    incorrect Prev link

    yasheshb's picture

    Hello,

    On the Cases page, prev link looks incorrect. i've filed an issue regarding it.

    rgd.

    yashesh

    p.s. have been using the new d.o site for a week now and looks great.

    it loosk great. I hope the

    taralushi's picture

    it loosk great. I hope the upgrade will be easy and some dynamic effect & animation are included.
    great job guys

    Cengolio.com umgesetzt mit Drupal.