Thanks Sameera for this comprehensive list.

We also need to test
1) External user stores (AD and OpenLDAP having larger number of
users/roles)
2) Volume testing (Create and publish a large number of assets)
3) Performance (When the store is loaded whether it takes considerable
amount of time time to load a page, etc...)
4) JDK versions (we can run this on java 8 ? IBM jdk ? )​

​5) With related to DBs, we also need to test with MSSQL.

@Nadeesha,
6) When setting up the cluster please note on following points (Sameera has
already mentioned most of the stuff)

   - All tests should be done with real network setup ( not localhost )
   - All tests should be done with non-standard ports
   - All tests should be done with an administration user other than
   admin/admin.
   - Testing for failure.

Regards,

Pavithra

On Thu, May 28, 2015 at 10:49 AM, Sameera Medagammaddegedara <
[email protected]> wrote:

> Hi,
>
> I have drafted an initial set of boundaries and use cases for the ES QA
> phase.This is a very limited set of scenarios and I may have missed several
> vital ones.Please feel free to add scenarios or boundary parameters that I
> have omitted.
>
> *Basic Scenarios*
>
> *Store*
>
>    - *UI*
>    - Browse the asset listing page (Anon and Logged In)
>       - Browse the asset details page (Anon and Logged In)
>       - Browse the top assets listing page (Anon and Logged In)
>       - Bookmark an asset
>       - Rate and write a review for an asset
>       - View bookmarked assets in the My Items page
>       - Search for an asset from the top assets listing page
>       - Search for an asset from an asset listing page
>       - Access the above pages with tenanted URLs (/t/)
>    - *API*
>       - Search for assets using the /assets API
>
> *Publisher*
>
>    - *UI*
>    - Create and publish an asset
>       - Tag an asset
>       - Update an asset
>       - Perform a lifecycle operation
>       - Search for an asset
>    - *API*
>       - All of the above scenarios
>       - Utilize the Authenticate and Logout endpoints
>
> The Store and Publisher scenarios should be  tested with the following
> user types:
>
>    - A super tenant user
>       - A super tenant admin
>       - A tenant user
>       - A tenant admin
>
> *Advance Scenarios*
>
>    - Clustered setup
>    - Extension model
>       - Adding a new asset type
>       - Overriding an existing view
>       - Adding a new view
>       - Overriding an existing API
>       - Adding a new API
>       - Customizing CRUD operations
>       - Add a new lifecycle
>       - Users having roles that have varying degrees of permissions
>    - External IDPs (See section on External IDPs)
>    - Changing the admin user and admin role
>    - Enable grouping
>
> *Databases*
>
>    - MYSQL
>    - POSTGRESQL
>    - ORACLE
>    - DB2
>
>
> *External IDPs*
>
>    - Shibboleth (https://shibboleth.net/)
>    - Identity Server 4.6.0 and 5.0.0
>
> *Browsers*
>
>    - IE 9+
>    - Firefox
>    - Chrome
>    - Safari
>    - Firefox Mobile (See *Additional Devices*)
>    - Chrome Mobile (See *Additional Devices*)
>
> *OSs*
>
> At the very minimum we should check if the pack starts in the following
> Operating Systems.
>
>    - Windows 7, Windows 8 , Windows Server 2008 (?) , Windows Server 2012
>    (?)
>    - Mac OS X
>    - Ubuntu , CentOS *[Any others?]*
>
>
> *Additional Devices *
>
> Check fluid layouts for external devices
>
>    - Tab
>    - Phone
>
> Thank You,
>
> Sameera
>
> --
> Sameera Medagammaddegedara
> Software Engineer
>
> Contact:
> Email: [email protected]
> Mobile: + 94 077 255 3005
>



-- 
*Pavithra Madurangi*
Associate Technical Lead - QA.
WSO2 Inc.: http://wso2.com/
Mobile: 0777207357 / 0112747089
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to