get-command -Verb Get
get-service (list services)
get-service –name
Ex: get-service -name Wsearch
start-service –name
Ex:start-service –name Wsearch
stop-service –name
Ex:stop-service –name Wsearch(stop services)
Get-Help Get-Service
Get-help set-service
Get-service
set-service –name wsearch –startuptype automatic/manual/disable
Get-command -Noun Service (see list of commands)
get-service (list services)
stop-service –name wsearch
get-service -name Wsearch
start-service –name Wsearch
get-service -name Wsearch
set-service –name wsearch –startuptype automatic
set-service –name wsearch –startuptype disabled
set-service –name wsearch –startuptype manual
============
b. Performance
i. All CPU, memory, disk, bandwidth etc., performance after the change will be recorded for PM’s reference. PM will decide if the change meet our release performance criteria.
ii. We need cover Cleanup based on clean up have a lot of sorting on the hash. However, because the bit of hash code is not changed. This would be lower priority.
c. Scalability
i. We can support 25 clients after the change without significant functionality issues when doing client backup
d. Longhaul
i. After the change, there won’t be resources leaks
e. Security
i. Double check the 128bit usage for SHA256 won’t raise significant security issue
===============
Accessibility
Thursday, October 27, 2011
3:43 PM
1. Selectable controls named and in proper tab order (more details later).
2. Access keys (e.g., pressing Alt plus some underlined letter clicks the button).
3. Aka "keyboard shortcuts" or "hotkeys" but we're not supposed to call them that anymore.
4. High contrast themes
Control Panel\Appearance and Personalization\Personalization
5. High DPI modes up to a custom text size of 200%
Control Panel\Appearance and Personalization\Display
Common Web Accessibility Bugs
6. Cannot set accessibility properties in html
Previous common bugs not obvious during CR.
Inferred by other means by browser.
7. Specify sizes in percentage
Test with zoom
8. Alternate text for images
Screen readers require context per control.
Not necessary if merely decorative
Localization/Globalization
Thursday, October 27, 2011
3:19 PM
Under-Localization:
The team will run manual tests on pseudo loc builds to look for strings that are not exposed for localization. Any string that’s not exposed for localization will be in English on the pseudo builds. The following strings must be localized:
• Strings exposed to the user.
• Tool tips.
• File version information – File description, copyrights, company name etc.
• URL – Links to online contents.
• Accelerator keys.
• Display file name.
• Service name and description in services.msc
• Firewall name and description.
• Event log entries.
Over-Localization:
Non-localizable strings should not be exposed for localization. Over localization typically results in functional bugs.
The following is the list of strings that should not be localized:
• Registry Key name and path
• Physical file name and folder name.
• Forwarded URLs.
• File extensions.
• Product names.
• Font names and sizes.
• Html and Xml tags.
i. Globalization test cases:
Loc specific testing on loc builds will be primarily done by the windows Intl test team but as feature area owners we should test the functionality is not dependent on any particular locale being present. The following are some areas that need to be considered by each feature team when creating loc test cases:
1. User Locale Awareness:
• Date and Time
Area Title
Calendar System
Check with non-Gregorian Calendars. Some of them are Japanese Emperor Era, Taiwan calendar, Korean Tangun Era calendar.
Date Formatting Change date format in regional settings.
Check with both Long date and short date formats.
Long Date
English (United States): Tuesday, August 7, 2007
Short Date
English (United States): 08/07/2007
Time Formatting Use a 12-hour or 24-hour clock.
Use a character other than “:” to separate hours/minutes/seconds. This can be set in the Advanced options for the regionals ettings.
Verify the date/time displayed in the console matches the user settings.
2. Keyboards and Input Methods
Area Title
IME/Keyboard layout Verify IME (Input Method Editor) support is present for EA languages.
The default keyboard layout should match the language.
International text Enter international text into all available input fields.
Cut/copy/paste international text.
Apply different types of fonts to international text.
3. Encoding and Unicode:
Area Title
Encoding and Unicode Verify the localized UI showed correctly on different system locale.
Verify the text displayed correctly with multilingual characters.
Make sure that text conversions between encodings that use different numbers of bytes per character do not cause buffer overflows, memory leaks, or text truncations
4. Sorting:
Area Title
Sort Check the correct sort result depends on user locale.
Compare the sort order of a collection before and after changing the user locale.
5. Turkish Specific
==============
Administrator:
Spanish (ES-ES) AdministraDor
French (FR-FR) AdministratEUR
German (DE-DE) Administrator
Japanese (JA-JP) Administrator
Quattro! (using local keyboard layout instead of English)
Spanish (ES-ES) Quattro!
French (FR-FR) Auqttro/
German (DE-DE) Quattro!
Japanese (JA-JP) Quattro!
Adding the EN-US keyboard layout:
1. Run intl.cpl (or find the Regional and Language Options in Control Panel… It has a globe on a stand icon).
2. Select the second tab (Languages), then click the button (Details) to launch the Text Services and Input Languages page.
3.
3. Here is a list of currently loaded keyboard input languages. Click the Add button to add a new language.
4. Click the top dropdown and select the language you’d like English (U.S.) and click OK. (See English Language & US Locale for Keyboard Input Languages table)
4. If you’d like that keyboard input language to be your default, click the dropdown above the list of installed keyboard languages and choose your preferred default language. When finished click OK until the dialogs are dismissed.
5. The Language Bar should now appear, floating or in the taskbar, and clicking it and selecting EN or another option will allow you to switch between input languages. Alt-Shift will also switch between each of the available input languages.
English Language & US Locale for Keyboard Input Languages
Spanish (ES-ES) Inglés (Estados Unidos)
French (FR-FR) Anglais (États-Unis)
German (DE-DE) Englisch (USA)
Japanese (JA-JP)
===================
Joe Strazzere - All Things Quality
Pasted from
March 8, 2009 - General Input Tests for Email Addresses
Posted in QA
Here are some routine tests to try for an email address field.
To use these values, you should first have some idea about the mechanism being used in your system to validate the email addresses. For example, many systems will attempt to validate email addresses when they are entered, but then follow up by attempting to send an email to the address. If no such email address exists, the address is rejected. If this is the case in your system, then you may need to substitute real addresses for the valid email addresses which follow the described pattern.
Then decide which of the following are relevant for your input field and use them.
If you are using an automated test tool, these values can easily be used exhaustively, or randomly, by a test script.
Valid Email Addresses
• email@domain.com
• firstname.lastname@domain.com
• first.name.last.name@domain.com
○ (some systems treat this as equal to firstnamelastname@domain.com)
• email@subdomain.domain.com
• firstname+lastname@domain.com
• 1234567890@domain.com
• email@domain-one.com
• _______@domain.com
• email@domain.name
• email@domain.co.jp
• firstname-lastname@domain.com
• email67890123456789012345678901234567890123456789012345678901234@domain.com
Valid, but rejected by some sites
• email@123.123.123.123
• email@[123.123.123.123]
• "email"@domain.com
• "firstname.lastname"@domain.com
• "firstname@lastname"@domain.com
Invalid Email Addresses
• name
• #@%^%#$@#$@#.com
• @domain.com
• firstname lastname
• email.domain.com
• email@domain@domain.com
• あいうえお@domain.com
• email@domain.com (firstname lastname)
• email@domain
• email@-domain.com
• email@111.222.333.44444
• email@domain..com
• email@domain.com.
Invalid, but accepted by some sites
• .email@domain.com
• email.@domain.com
• email..email@domain.com
• email@domain.web
April 5, 2009 - Added valid email containing several periods within.
Charles S van der Linden said "Multiple periods before the @ are allowed by many eg. john.van.der.tester@gmail.com will work. (gmail actually strips all the periods so that address maps to the same thing without the periods before the @ sign)."
March 25, 2009 - Added invalid email with a trailing period.
Heather Noggle said "I always also validate to be sure e-mail addresses don't end with a dot. A lot of people copy e-mail addresses out of text, and the e-mail address in that text is followed by a period to make sense in normal written English. Lots of non-savvy computer users will just go ahead and copy that dot if they're not directly clicking through."
Pasted from
=======================
Posts
