Verson 1 testing

I will use the same mind map for version one testing since version 1 functionality collate closely with each other

Get Started. It's Free
or sign up with your email address
Rocket clouds
Verson 1 testing by Mind Map: Verson 1 testing

1. Stories for Sprint 2

1.1. MSSP-50 REQ_21 Log into existing account

1.1.1. Login Page building

1.1.2. Successful login attempt

1.1.3. Invalid login attempt

1.1.3.1. Unregistered user

1.1.3.1.1. Not supported

1.1.3.1.2. not registered

1.1.3.2. Not activated user

1.1.3.2.1. user hasn't activated yet

1.1.3.2.2. unsuccessful activation

1.1.3.3. Account locked down

1.1.3.3.1. Same browser

1.1.3.3.2. Different browser

1.1.3.3.3. Different devices

1.1.3.4. Incorrect inputs

1.1.3.4.1. Wrong username

1.1.3.4.2. Wrong password

1.1.3.4.3. Wrong username and password

1.1.3.4.4. Invalid Email address ie; [email protected]

1.1.3.5. Missing inputs

1.1.3.5.1. Email missing

1.1.3.5.2. Password missing

1.1.3.5.3. Missing email and password

1.1.4. System down

1.1.4.1. Front end SSP down

1.1.4.2. Back-end velocity down

1.2. MSSP-46 REQ_34 Link back to homepage

1.2.1. Clicking on the logo

1.3. MSSP-54 REQ_18 Trigger self-service welcome notification

1.3.1. welcome email

1.3.2. email links

1.3.3. Triggering

1.4. MSSP-47 REQ_30 Access Personal Homepage

1.4.1. Look and feel

1.5. MSSP-61 REQ_106 Notification and alert methods

1.5.1. Check Mandrill emails

1.5.2. Test in Mandrill Test mode

1.5.3. Make sure correct variables get passed for different environments

1.5.4. Risk - Mandrill failure scenario ?

1.5.4.1. no template

1.5.4.2. template does not have variables set up

1.6. MSSP-55 REQ_13 Self-service account activation management

1.6.1. Active token

1.6.2. Expired token

1.6.3. Incorrect token

1.6.4. Different screens for expired and incorrect tokens

1.6.5. Password set screen

1.6.6. Password rules and validation

1.6.7. Terms and conditions

1.6.8. automatic login

1.7. MSSP-45 REQ_151 Manual Customer Registration

1.7.1. Test with mock services ?

1.7.2. Test data set up ?

1.7.3. How to handle the activation email ?

2. Data set up and Tear down

2.1. Need to set up data in velocity

2.2. Need to tear down data in velocity

2.3. Should not be mock ups, should be the read deal

3. Constrains

3.1. Do you mind if your test data gets deleted at the end of each sprint deployment ? until SSP is stable ?

3.2. Talking to Velocity / Test environments

4. Non functional testing

4.1. how the visuals will be tested

4.2. How emails will be tested

4.3. What non functional you going to target ?

4.4. Responsive Design

5. Test data set up

5.1. Residential customers

5.2. SMB

5.3. Agri

5.4. BOL

6. Stories from Sprint 3

6.1. MSSP-49 REQ_28 Manual Logout

6.1.1. logout option

6.1.2. logout redirect

6.1.3. post logout screen

6.2. MSSP-48 REQ_29 Automatically Terminate Inactive Session

6.2.1. Inactive session error

6.2.2. inactive redirecting

6.2.3. Remember state after session time out ? NFS

6.2.4. Client call after session timeout

6.3. Spikes

6.3.1. Using segement hooks

6.3.1.1. Objectives

6.3.1.1.1. How to integrate with Intercom

6.3.1.1.2. Getting user feedback from Qualaroo

6.3.1.1.3. Implementation documentation

6.3.1.1.4. Getting accounts and environments set up

6.3.1.2. Set up test accounts for Meridian test ?

6.3.2. intercom configuration

6.3.2.1. Objectives

6.3.2.1.1. what can we and cant we do from intercom ? ie Rendering

6.3.2.1.2. Implementation documentation

6.3.2.1.3. Gettung accounts and environments set up

6.3.2.2. Set up test account for Meridian testing ?

6.4. MSSP-60 REQ_159 Performance Monitoring

6.4.1. Set up environments

6.4.2. understand how it works

6.4.3. Set up accounts

6.5. MSSP-62 REQ_09 Addressable pages

6.5.1. Pages aren't directly without login to the system when required

6.5.2. Check all email links

6.5.3. URLs construction is inline with the Meridian requirement

6.6. Internal stories

6.6.1. MSSP-74 Global switch off for analytic - for testing

7. Environments

7.1. What Environment for Initial System integration testing ?

7.2. What are other options ?

7.3. How do we set up test data ?

7.4. Can we get a road map for environments ?

7.5. Can we get a dependency map for the test environments ? so everyone knows what is talking to what ?

8. Backlog

8.1. MSSP-52 REQ_20 Request forgotten password reset

8.1.1. Valid customer

8.1.1.1. Multiple reset attemps

8.1.1.2. successfull reset attempt

8.1.1.2.1. Redirection

8.1.1.2.2. Reset password screen

8.1.1.2.3. Email

8.1.1.3. life cycle issues

8.1.1.3.1. multiple reset attempts

8.1.1.3.2. Locked out user trying to reset password

8.1.1.3.3. deactivated user trying to reset password

8.1.2. invalid customer

8.1.2.1. Unregistered customers

8.1.2.2. Not activated customers

8.1.2.3. Not supported customers

8.1.2.4. invalid Email address

8.2. MSSP-51 REQ_20 Access Meridian contact details

8.2.1. look and feel

9. Enterprise Caching

9.1. We are still breaking the stories down to small chunks

9.2. Will be an isolated piece of work sitting alone

9.3. How can you test this ? this won't have a web front end to test