11 1 Deployment Test Plan

· Opened by johnataylor 8 hours ago

· Verify tool tips across browsers (IE7+, C, FF, S, O)

· Culture-specific scenarios for decimal separators:

· German

· Hindi

· Accessibility spot-check

· Screen reader compatibility (JAWS, NVDA)

· Opened by anurse 5 days ago

· Verify Andrew's test note scenarios (below)

· Perform P0 scenarios with RequireSSL turned on and off on the server.

· Log in and log out, verify cookies through Fiddler

· We register the route "OwinRoute"

· Try to upload with multiple API Key credentials in the table -- I think we throw up, but it's good to double-check

· What happens if two users ever have the same API Key? How do we handle the error?

· Fail authorization, verify error message (password and API Key)

Andrew's Test Notes

· Create some SHA1-password users before deployment (I'll send out instructions)

· Log in with various users having PBKDF2 ("new") and SHA1 ("old") passwords, verify that SHA1 passwords are replaced (instructions to come)

· Log off and try to directly hit a URL like "/account", verify redirect to login page and redirect back to "/account" after login

· Upload packages through the GUI

· Upload packages through NuGet push API

· Use NuGet push with no API Key -> Get Username prompt

· Use NuGet push with bogus API Key -> Get Forbidden response

· Use NuGet push with API key that doesn't own package -> Get Forbidden response

· Log in, then navigate to "http://[nuget site root]/" -> Redirects to SSL Homepage

· Log off, verify that the following Cookies are NOT present: ".AspNet.Cookies", ".ForceSSL"

· Opened by TimLovellSmith 10 days ago

TimLovellSmith referenced this issue from a commit 10 days ago

	TimLovellSmith	Fix #1648 - error page looking wrong with no background image.	4da78f3

Provide feedback