Skip to content

12 20 deployment test plan

Jump to bottom
claycompton edited this page Dec 10, 2013 · 1 revision

·         #1773
Change "Remove" button on Password Login widget to "Disable" 2 - In Review

9419E18C-6A55-44DB-9815-1980C0E919B0.jpg

·         Opened by anurse 4 days ago

Issue #1778: Account details page has "Microsoft Account" in the "more info" for Microsoft account

Pull Request #1782: Fix #1773 and #1778 by tweaking text

Component:  UI

 

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

·         Accessibility spot-check

·         Screen reader compatibility (JAWS, NVDA)

 

·         #1750
Validation message for contacting support is wrong 2 - In Review

100C032F-BD1E-402D-BEBC-6A5D0042137F.png

·         Opened by jeffhandley 12 days ago

Pull Request #1769: Fixed error message in ReportMypackage form

Component:  UI

 

·         Report abuse with a valid reason and message

·         Report abuse with a valid reason and no message

·         Report abuse with an invalid reason, verify error

·         Verify experience for Report Abuse and Contact Owners is unchanged.

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

·         Accessibility spot-check

·         Screen reader compatibility (JAWS, NVDA)

 

·         #1745
Add package validation for the MinClientVersion attribute 2 - In Review

609C38D4-4135-4D33-A905-BE491D53ABC3.jpg

·         Opened by jeffhandley 14 days ago

·         1 comment

 

·         #1682
"Oh, no!" error page when uploading a package with an invalid license URL Priority - 3 2 - In Review

38389ACB-FC80-4FF2-8D6D-9906A91D16D1.jpg

·         Opened by claycompton a month ago

·         4 comments

Issue #1681: Uploading a package with an invalid Project or Icon URL is blocked at verify-upload with no on-screen validation error.

 

Pull Request #1743: Fix #1682 by adding some additional validation

Component:  UI

 

·         Contrive different kinds of metadata errors, verify validation error in site when uploading package:

·         No metadata

·         Invalid Metadata XML

·         Missing required fields

·         Exceeding each field's length

·         Non-URL values in URL fields

·         Non-version strings in version field

·         Invalid Min Client version

·         Invalid protocols in URL fields

·         Bad string (invalid UTF-8)

·         Wrong Author/Owner

·         Invalid language identifier

·         Bad assembly references

·         Use a URL value of 2,082 chars in a package, verify no error.

·         Use a URL value that exceeds 2,083 chars, verify error.

·         Report abuse with a valid reason and message

·         Report abuse with a valid reason and no message

·         Report abuse with an invalid reason, verify error

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

·         Accessibility spot-check

·         Screen reader compatibility (JAWS, NVDA)

 

·         #1729
Update Dependent Packages 2 - In Review

B57BA4B3-AC81-477C-973B-51EA129D9073.jpg

·         Opened by claycompton a month ago

·         1 comment

Pull Request #1742: Fix #1729 by updating some packages

Component:  N.A.

 

·         Revisit package management scenarios

 

·         #1724
Unify the user experience when choosing inappropriate reasons on the Report Abuse page 2 - In Review

C5798D46-2FCF-4C5E-8B79-835087B4C783.png

·         Opened by claycompton a month ago

Pull Request #1770: RebortAbuse And LicenseReportVisiblity fixes

Pull Request #1781: Combined error message in ReportAbuse

Component:  UI

 

·         Use invalid reason for reporting abuse (HasABugOrFailedToInstall), verify error treatment

·         Use each valid reason for reporting abuse, verify no validation error and verify message receipt.

·         Send Contact Owner and Contact Support e-mails, verify no change in behavior.

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

·         Accessibility spot-check

·         Screen reader compatibility (JAWS, NVDA)

 

·         #1720
JSON error in logs when accessing stats page for a package with no downloads. 2 - In Review

FC8B9696-6D09-4D20-B91F-9C8541717BF3.png

·         Opened by claycompton a month ago

Pull Request #1768: Avoid flooding elmah logs with stats related errors

 

Component:  UI

 

·         Attempt repro scenario, verify no error is logged.

·         Verify stats for new and existing packages.

 

·         #1680
Unfulfilled Sign In / Register Feedback 2 - In Review

50B9E01E-7FFE-4B13-8BBB-E8784366DDE5.jpg

·         Opened by claycompton a month ago

·         1 comment

Pull Request #1744: Fix #1680 by tweaking the thanks page

Component:  UI

 

·         Go through sign-in process by creating a site account, verify:

·         link to view profile on Thanks page.

·         limited number of clicks to see your profile.

·         Repeat process starting from a never-before-seen Microsoft account, verify user sees same "Thanks" page at the end.

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

·         Accessibility spot-check

·         Screen reader compatibility (JAWS, NVDA)

 

·         #1679
In Package Version lists, Boldface and default item selection don't align if there are newer listed prerelease packages. 2 - In Review

958F2A02-36C7-45FD-8B5D-17908D85D8D6.jpg

·         Opened by claycompton a month ago

·         1 comment

Pull Request #1746: Fix #1679 by cleaning up the latest markers

Component:  UI

 

·         Create packages whose versions have the following attributes:

·         Latest version is pre-release

·         Last two versions are pre-release

·         Last version is unlisted

·         Last is unlisted, previous is pre-release

·         Last is pre-release, previous is unlisted

·         All versions are unlisted

·         All versions are pre-release

·         Navigate to package page (without version) and verify package details.  Confirm:

·         "this version" marker on stable, pre-release, and unlisted packages

·         "latest" marker and boldface highlighting always match and are on stable packages.

·         Verify from both package owner and regular user accounts.

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

·         Accessibility spot-check

·         Screen reader compatibility (JAWS, NVDA)

 

·         #1670
Fixes to WebMatrix curated feed 2 - In Review

A462564E-9932-4EE7-94F8-34F0DE63A960.jpg

·         Opened by jeffhandley 2 months ago

·         3 comments

Issue #1311: WebMatrix curated feed should also hide packages depending on packages that require Powershell

Pull Request #1747: Fix #1670 by improving WebMatrix curation

Component:  OData

 

·         Powershell dependency

·         Create a package that uses a PowerShell script, verify not in WebMatrix feed.

·         Create a package with a dependency on a package with a Powershell script, verify not present in WebMatrix feed.

·         Try with even longer chains of dependency.

·         Try with init.ps1, install.ps1, uninstall.ps1, and other file names.

·         Verify order dependency (When uploading two packages, A and B, in that order, IF A is otherwise WebMatrix compatible (see issue) EXCEPT that it is dependent upon B which IS NOT WebMatrix compatible, then A is expected to be added to the WebMatrix feed)

·         Framework requirements:

·         Try with 4.5-only packages.

·         Try with dependencies on older .NET Framework versions

·         MinClient requirements:

·         version is null

·         Version is out-of-range

·         Version is in range.

·         T4 requirement:

·         File exists

·         File does not exist

·         Other scenarios:

·         IsLatestStable verification

·         Aspnetwebpages tag

 

 
Clone this wiki locally