mahara-contributors team mailing list archive

[Steven <stevens@xxxxxxxxxxxxxxx>]

Public bug reported:

Update Existing Behat feature file 
------------------------------------
Behat test: Settings > User_themes.feature already exists - need to update behat test to include the following: 


Verify Themes:
1.Have been present in Mahara in their current form since 1.2.
2. Must be uploaded directly onto the web server by a system administrator.
3. Can override the page template for every single screen in Mahara, giving total control over how everything is displayed.
4. Depending on site and institution settings, there may be:
 a single theme for the whole site
 a theme for every institution
 the possibility for users to choose their own theme for browsing the site
 the possibility for users to apply a particular theme to each portfolio page, the page themes

Verify Skins:
1. Can be created, shared, exported and uploaded by users via Portfolio then Skins.
2. Are less powerful than themes. They can only change page colours, fonts and background images, and add extra CSS. Basically they add one additional user-controlled CSS stylesheet to a page.
3.Can only be applied to user-created portfolio pages. They don’t change the way any other part of Mahara is displayed.

Verify following rules apply:

1.If users apply a skin to one of their pages, it adds one additional CSS stylesheet to the page. This is in addition to the CSS from the theme.
2.Naturally, any particular skin might not look good in all themes, especially if the theme has changed the underlying page templates for portfolio pages.
3.If you’re a theme designer, the good news is that the skin stylesheet is itself a page template (skin/style.tpl). So, you can specify which page elements each of the skin settings should apply to by overriding that page template.

** Affects: mahara
     Importance: Undecided
     Assignee: Steven (stevens-q)
         Status: In Progress

** Changed in: mahara
       Status: New => In Progress

** Changed in: mahara
     Assignee: (unassigned) => Steven (stevens-q)

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1755049

Title:
  behat test for themes

Status in Mahara:
  In Progress

Bug description:
  Update Existing Behat feature file 
  ------------------------------------
  Behat test: Settings > User_themes.feature already exists - need to update behat test to include the following: 

  
  Verify Themes:
  1.Have been present in Mahara in their current form since 1.2.
  2. Must be uploaded directly onto the web server by a system administrator.
  3. Can override the page template for every single screen in Mahara, giving total control over how everything is displayed.
  4. Depending on site and institution settings, there may be:
   a single theme for the whole site
   a theme for every institution
   the possibility for users to choose their own theme for browsing the site
   the possibility for users to apply a particular theme to each portfolio page, the page themes

  Verify Skins:
  1. Can be created, shared, exported and uploaded by users via Portfolio then Skins.
  2. Are less powerful than themes. They can only change page colours, fonts and background images, and add extra CSS. Basically they add one additional user-controlled CSS stylesheet to a page.
  3.Can only be applied to user-created portfolio pages. They don’t change the way any other part of Mahara is displayed.

  Verify following rules apply:

  1.If users apply a skin to one of their pages, it adds one additional CSS stylesheet to the page. This is in addition to the CSS from the theme.
  2.Naturally, any particular skin might not look good in all themes, especially if the theme has changed the underlying page templates for portfolio pages.
  3.If you’re a theme designer, the good news is that the skin stylesheet is itself a page template (skin/style.tpl). So, you can specify which page elements each of the skin settings should apply to by overriding that page template.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1755049/+subscriptions