Run Commands

Some of the useful Run commands in Windows


Here is a list of commands that you can be used with the Run command prompt in Windows. Most of the commands can be used in all the Windows operating systems and some are dependent on the softwares/plug-ins installed in your computer.

Program Run Command:


Accessibility Controls = access.cpl
Accessibility Wizard = accwiz
Add Hardware Wizard = hdwwiz.cpl
Add/Remove Programs = appwiz.cpl
Administrative Tools = control admintools
Adobe Acrobat ( if installed ) = acrobat
Adobe Distiller ( if installed ) = acrodist
Adobe ImageReady ( if installed ) = imageready
Adobe Photoshop ( if installed ) = photoshop
Automatic Updates = wuaucpl.cpl
Basic Media Player = mplay32
Bluetooth Transfer Wizard = fsquirt

Calculator = calc
Ccleaner ( if installed ) = ccleaner
C: Drive = c:
Certificate Manager = cdrtmgr.msc
Character Map = charmap
Check Disk Utility = chkdsk
Clipboard Viewer = clipbrd
Command Prompt = cmd
Command Prompt = command
Component Services = dcomcnfg
Computer Management = compmgmt.msc
Compare Files = comp
Control Panel = control
Create a shared folder Wizard = shrpubw

Date and Time Properties = timedate.cpl
DDE Shares = ddeshare
Device Manager = devmgmt.msc
Direct X Control Panel ( if installed ) = directx.cpl
Direct X Troubleshooter = dxdiag
Disk Cleanup Utility = cleanmgr
Disk Defragment = dfrg.msc
Disk Partition Manager = diskmgmt.msc
Display Properties = control desktop
Display Properties = desk.cpl
Display Properties (w/Appearance Tab Preselected ) = control color
Dr. Watson System Troubleshooting Utility = drwtsn32
Driver Verifier Utility = verifier

Ethereal ( if installed ) = ethereal
Event Viewer = eventvwr.msc
Files and Settings Transfer Tool = migwiz
File Signature Verification Tool = sigverif
Findfast = findfast.cpl
Firefox = firefox
Folders Properties = control folders
Fonts = fonts
Fonts Folder = fonts
Free Cell Card Game = freecell

Game Controllers = joy.cpl
Group Policy Editor ( xp pro ) = gpedit.msc
Hearts Card Game = mshearts
Help and Support = helpctr
Hyperterminal = hypertrm
Hotline Client = hotlineclient

Iexpress Wizard = iexpress
Indexing Service = ciadv.msc
Internet Connection Wizard = icwonn1
Internet Properties = inetcpl.cpl
Internet Setup Wizard = inetwiz
IP Configuration (Display Connection Configuration) = ipconfig /all
IP Configuration (Display DNS Cache Contents) = ipconfig /displaydns
IP Configuration (Delete DNS Cache Contents) = ipconfig /flushdns
IP Configuration (Release All Connections) = ipconfig /release
IP Configuration (Renew All Connections) = ipconfig /renew
IP Configuration (Refreshes DHCP & Re-Registers DNS) = ipconfig /registerdns
IP Configuration (Display DHCP Class ID) = ipconfig /showclassid
IP Configuration (Modifies DHCP Class ID) = ipconfig /setclassid

Java Control Panel ( if installed ) = jpicpl32.cpl
Java Control Panel ( if installed ) = javaws
Keyboard Properties = control keyboard

Local Security Settings = secpol.msc
Local Users and Groups = lusrmgr.msc
Logs You Out of Windows = logoff

Malicious Software Removal Tool = mrt
Microsoft Access ( if installed ) = access.cpl
Microsoft Chat = winchat
Microsoft Excel ( if installed ) = excel
Microsoft Diskpart = diskpart
Microsoft Frontpage ( if installed ) = frontpg
Microsoft Movie Maker = moviemk
Microsoft Management Console = mmc
Microsoft Narrator = narrator
Microsoft Paint = mspaint
Microsoft Powerpoint = powerpnt
Microsoft Word ( if installed ) = winword
Microsoft Syncronization Tool = mobsync
Minesweeper Game = winmine
Mouse Properties = control mouse
Mouse Properties = main.cpl
MS-Dos Editor = edit
MS-Dos FTP = ftp

Nero ( if installed ) = nero
Netmeeting = conf
Network Connections = control netconnections
Network Connections = ncpa.cpl
Network Setup Wizard = netsetup.cpl
Notepad = notepad
Nview Desktop Manager ( if installed ) = nvtuicpl.cpl

Object Packager = packager
ODBC Data Source Administrator = odbccp32
ODBC Data Source Administrator = odbccp32.cpl
On Screen Keyboard = osk
Opens AC3 Filter ( if installed ) = ac3filter.cpl
Outlook Express = msimn

Paint = pbrush
Password Properties = password.cpl
Performance Monitor = perfmon.msc
Performance Monitor = perfmon
Phone and Modem Options = telephon.cpl
Phone Dialer = dialer
Pinball Game = pinball
Power Configuration = powercfg.cpl
Printers and Faxes = control printers
Printers Folder = printers
Private Characters Editor = eudcedit

Quicktime ( if installed ) = quicktime.cpl
Quicktime Player ( if installed ) = quicktimeplayer

Real Player ( if installed ) = realplay
Regional Settings = intl.cpl
Registry Editor = regedit
Registry Editor = regedit32
Remote Access Phonebook = rasphone
Remote Desktop = mstsc
Removable Storage = ntmsmgr.msc
Removable Storage Operator Requests = ntmsoprq.msc
Resultant Set of Policy ( xp pro ) = rsop.msc

Scanners and Cameras = sticpl.cpl
Scheduled Tasks = control schedtasks
Security Center = wscui.cpl
Services = services.msc
Shared Folders = fsmgmt.msc
Sharing Session = rtcshare
Shuts Down Windows = shutdown
Sounds Recorder = sndrec32
Sounds and Audio = mmsys.cpl
Spider Solitare Card Game = spider
SQL Client Configuration = clicongf
System Configuration Editor = sysedit
System Configuration Utility = msconfig
System File Checker Utility ( Scan Immediately ) = sfc /scannow
System File Checker Utility ( Scan Once At Next Boot ) = sfc /scanonce
System File Checker Utility ( Scan On Every Boot ) = sfc /scanboot
System File Checker Utility ( Return to Default Settings) = sfc /revert
System File Checker Utility ( Purge File Cache ) = sfc /purgecache
System File Checker Utility ( Set Cache Size to Size x ) = sfc /cachesize=x
System Information = msinfo32
System Properties = sysdm.cpl

Task Manager = taskmgr
TCP Tester = tcptest
Telnet Client = telnet
Tweak UI ( if installed ) = tweakui
User Account Management = nusrmgr.cpl
Utility Manager = utilman

Volume Serial Number for C: = label
Volume Control = sndvol32
Windows Address Book = wab
Windows Address Book Import Utility = wabmig
Windows Backup Utility ( if installed ) = ntbackup
Windows Explorer = explorer
Windows Firewall = firewall.cpl
Windows Installer Details = msiexec
Windows Magnifier = magnify

Windows Management Infrastructure = wmimgmt.msc
Windows Media Player = wmplayer
Windows Messenger = msnsgs
Windows Picture Import Wizard (Need camera connected) = wiaacmgr
Windows System Security Tool = syskey
Windows Script host settings = wscript
Widnows Update Launches = wupdmgr
Windows Version ( shows your windows version ) = winver
Windows XP Tour Wizard = tourstart
Wordpad = write
Zoom Utility = igfxzoom




Join our community in Facebook and Google+ at the below URL's to stay up to date:



Short Cut Keys

Some useful Short Cut Keys


Hey Guys, I just came across the list of short cut keys which would help all our IT/ITES people to work smartly and quickly. I thought this would help us. Though most of the short cuts listed below would be known to most of you people, but I guess this would be of little help to some.  Please share this with your friends so that they are also aware of it.

Some useful shortcuts...

Useful Shortcut:
Start + M: Minimizes all open windows
Start + Shift + M: Maximizes All Windows
Start + E: Runs Windows Explorer
Start + R: Open the RUN Dialog Box
Start + F: Open the Search Results Dialog box
Start + CTRL + F: Opens the Search Results-Computer dialog Box (if the computer is connected to a network)
Start + Pause (Break): Opens the System Properties Dialog Box

Windows System Key Combinations:
F1: Help
CTRL + ESC: Open Start menu
ALT + TAB: Switch between open programs
ALT + F4: Quit program
SHIFT + DELETE: Delete item permanently

Windows Program Key Combinations :
CTRL + C: Copy
CTRL + X: Cut
CTRL + V: Paste
CTRL + Z: Undo
CTRL + B: Bold
CTRL + U: Underline
CTRL + I: Italic

Mouse Click/Keyboard Modifier Combinations for Shell Objects :
SHIFT + right click: Displays a shortcut menu containing alternative commands
SHIFT + double click: Runs the alternate default command (the second item on the menu)
ALT + double click: Displays properties
SHIFT + DELETE: Deletes an item immediately without placing it in the Recycle Bin

General Keyboard-Only Commands :
F1: Starts Windows Help
F10: Activates menu bar options
SHIFT + F10 : Opens a shortcut menu for the selected item (this is the same as right-clicking an object
CTRL + ESC: Opens the Start menu (use the ARROW keys to select an item)
CTRL + ESC or ESC: Selects the Start button (press TAB to select the taskbar, or press SHIFT+F10 for a context menu)
ALT + DOWN ARROW: Opens a drop-down list box
ALT + TAB: Switch to another running program (hold down the ALT key and then press the TAB key to view the task-switching window)
SHIFT: Press and hold down the SHIFT key while you insert a CD-ROM to bypass the automatic-run feature
ALT + SPACE: Displays the main window's System menu (from the System menu, you can restore, move, resize, minimize, maximize, or close the window)
ALT +- (ALT + hyphen): Displays the Multiple Document Interface (MDI)child window's System menu (from the MDI child window's System menu, you can restore, move, resize, minimize, maximize, or close the child window)
CTRL + TAB: Switch to the next child window of a Multiple Document Interface (MDI) program
ALT + underlined letter in menu: Opens the menu
ALT + F4: Closes the current window
CTRL + F4: Closes the current Multiple Document Interface (MDI) window
ALT + F6: Switch between multiple windows in the same program (for example, when the Notepad Find dialog box is displayed
ALT + F6 : switches between the Find dialog box and the main Notepad window)

Shell Objects and General Folder/Windows Explorer Shortcuts For a selected object:
F2: Rename object
F3: Find all files
CTRL + X: Cut
CTRL + C: Copy
CTRL + V: Paste
SHIFT + DELETE: Delete selection immediately, without moving the item to the Recycle Bin
ALT + ENTER: Open the properties for the selected object
To Copy a File: Press and hold down the CTRL key while you drag the file to another folder.
To Create a Shortcut: Press and hold down CTRL+SHIFT while you drag a file to the desktop or a folder.

General Folder/Shortcut Control:
F4: Selects the Go To A Different Folder box and moves down the entries in the box (if the toolbar is active in Windows Explorer)
F5: Refreshes the current window.
F6: Moves among panes in Windows Explorer
CTRL + G: Opens the Go To Folder tool (in Windows 95 Windows Explorer only)
CTRL + Z: Undo the last command
CTRL + A: Select all the items in the current window
BACKSPACE: Switch to the parent folder
SHIFT + click + Close button: For folders, close the current folder plus all parent folders

Windows Explorer Tree Control:
Numeric Keypad *: Expands everything under the current selection
Numeric Keypad +: Expands the current selection
Numeric Keypad -: Collapses the current selection.
RIGHT ARROW: Expands the current selection if it is not expanded, otherwise goes to the first child
LEFT ARROW: Collapses the current selection if it is expanded, otherwise goes to the parent

Properties Control:
CTRL + TAB/CTRL + SHIFT + TAB: Move through the property tabs

Accessibility Shortcuts:
Press SHIFT five times: Toggles StickyKeys on and off
Press down and hold the right SHIFT key for eight seconds: Toggles FilterKeys on and off
Press down and hold the NUM LOCK key for five seconds: Toggles ToggleKeys on and off
Left ALT + left SHIFT+NUM LOCK: Toggles MouseKeys on and off
Left ALT + left SHIFT+PRINT SCREEN: Toggles high contrast on and off

Microsoft Natural Keyboard Keys:
Windows Logo: Start menu
Windows Logo + R: Run dialog box
Windows Logo + M: Minimize all
SHIFT + Windows Logo+M: Undo minimize all
Windows Logo + F1: Help
Windows Logo + E: Windows Explorer
Windows Logo + F: Find files or folders
Windows Logo + D: Minimizes all open windows and displays the desktop
CTRL + Windows Logo + F: Find computer
CTRL + Windows Logo + TAB: Moves focus from Start, to the Quick Launch toolbar, to the system tray (use RIGHT ARROW or LEFT ARROW to move focus to items on the Quick Launch toolbar and the system tray)
Windows Logo + TAB: Cycle through taskbar buttons
Windows Logo + Break: System Properties dialog box
Application key: Displays a shortcut menu for the selected item

Microsoft Natural Keyboard with IntelliType Software Installed:
Windows Logo + L: Log off Windows
Windows Logo + P: Starts Print Manager
Windows Logo + C: Opens Control Panel
Windows Logo + V: Starts Clipboard
Windows Logo + K: Opens Keyboard Properties dialog box
Windows Logo + I: Opens Mouse Properties dialog box
Windows Logo + A: Starts Accessibility Options (if installed)
Windows Logo + SPACEBAR: Displays the list of Microsoft IntelliType shortcut keys
Windows Logo + S: Toggles CAPS LOCK on and off

Dialog Box Keyboard Commands:
TAB: Move to the next control in the dialog box
SHIFT + TAB: Move to the previous control in the dialog box
SPACEBAR: If the current control is a button, this clicks the button. If the current control is a check box, this toggles the check box. If the current control is an option, this selects the option.
ENTER: Equivalent to clicking the selected button (the button with the outline)
ESC: Equivalent to clicking the Cancel button
ALT + underlined letter in dialog box item: Move to the corresponding item


Join our community in Facebook and Google+ at the below URL's to stay up to date:

Facebook Page: http://www.facebook.com/SoftwareQaHelp
Google+ : https://plus.google.com/101680718973348361876

Some more checklist

As promised earlier, I'm writing few more requirements that would help you folks in preparing for testing. As always, I would request you all to post your comments so that all the testers could make their job easier. If you have missed to read the other checklists, please Click here.

 

Deployment or Release management requirements



  • Version control is applied to all development products and system documentation, it is highly recommended to use a SVN or rational Clear-case or Git something would be good instead of manual.
  • Deployments are always done from 1 agreed central data store
  • Roll-back scenario's are in place for every deployment cycle
  • Users (both the dev team and the testing team) are trained and informed about deployment agreements
  • A patch procedure is known, documented and implemented
  • Deployment tasks follow formalized checklists (should be verified by the test team)
  • Builds or data refreshes in a test environment take only place after approval of the impacted test teams
  • A deployment/release management role is assigned
  • Every defect fixed for a new deployment in the test environment is at least communicated within an agreed defect management tool
  • Every deployment should come along with the build release note
  • Builds are subject to formal and/or informal entry criteria


Maintainability requirements


    Procedures to add/delete or update hardware components are existing and followed
    The test environment components are sized in relation to the production environment
    Log files are available for the different applications deployed on the test environment
    Disaster recovery plan is known, documented, implemented and trained to everyone in the team
    Procedure exists to request and add test users for any application in the test environment
    Unexpected downtime of the test environment is communicated to all the stakeholders (preferably using a central communication channel - for instance an intranet website to avoid miscommunication and other issues)
    Physical locations of different infrastructural components are identical to the production environment and documented. Any deviation is clearly identified and approved by the project team

We are agile enough to patch and refresh data properly which improved the test experience drastically.



Join our community in Facebook and Google+ at the below URL's to stay up to date:

Facebook Page: http://www.facebook.com/SoftwareQaHelp
Google+ : https://plus.google.com/101680718973348361876




Test Data Requirements

Test data requirements


Earlier I have promised you folks that I would write about the list of requirements that we need to meet in all the stages of testing (in List of Requirements) and I guess I have already shared the testability requirements. In this section, I would talk about the requirements that are needed to set the test data in the staging server.
  • Any production data loaded into the test environment is scrambled in a way that it still fits logically together but is impossible to link back to actual clients in the production database.
  • Create a back-up and restore procedure which does not take longer than 4 working hours.
  • Create a back-up and restore procedure which should be possible at least on a weekly basis with a lead time of 1 working day.
  • A representative set of production(like) test data can be unloaded in the test environment.
  • Back-up and restore procedures exist to back-up and release a partial or full data extract.
  • Full Data refresh with scrambled production data is possible on request  with a lead time of at least 1 working week.
  • Make sure a procedure to request for a data is implemented.

Please share in your inputs in all the stages so that we could put together and help our friends online.

Join our community in Facebook and Google+ at the below URL's to stay up to date:

Facebook Page: http://www.facebook.com/SoftwareQaHelp
Google+ : https://plus.google.com/101680718973348361876





List of requirements and checklist in all the stages of testing

I guess most of you would have missed some important task which should have been done earlier before starting to test. To be open I had came across such situations many times. In order to overcome this, I am creating the checklist for all the tasks in the testing phase. For now I have added few and will keep adding the details. Follow this blog or bookmark it to your favorites to see the updates.

To start building our integration test environment.


Testability requirements

  • All applications that exists or to be delivered in the production have to be available or simulated in the test environment. 
  • Getting the list of settings and configurations is available along with the comparisons of the settings and configurations of the production environment is necessary.
  • Get the required tools and licenses ready for testers (If tools can not be provided due to licensing issues, try to put in a work-around is in place to facilitate testing)
  • If the application is going to use any front end devices to access software through different channels (like phones, card readers, GPS Units, desk tops, laptops, pads,...) get that in place
  • Batch procedures are internally controllable and automated as in a production environment (manual trigger, start, pause, stop batch procedures)
  • Measuring tools should be in place to enable monitoring the communication between applications and application layers.
  • External Connectivity to test environments for support, deployment and testing should be ready
  • Database read access is required for all testers
  • Make sure that the Input/output simulators are in place and documented for every interface type
  • At least 1 test user exists for every defined role in the application under test
  • Time traveling is possible in at least one of the following means: "time goes by faster (eg: 1 week = 1 hour)", "move forward and reset from a defined time in the future", "coherent data creation/update to a  time stamp in the past"
  • All configurations of the different interfacing systems within the test environment have to be centrally managed
  • The test infrastructure has an availability of 95% (planned deployments are not included)
  • Defects are centrally managed, using 1 agreed defect managing system and flow 

I would highly recommend you all to have a look at the other requirements, which I have prepared. 
The checklist of Test data requirements -  Test Data Requirements
The checklist for Deployment/Release management requirements -  Deployment or Release management requirements
The checklist for Maintainability requirements - Maintainability requirements

Join our community in Facebook and Google+ at the below URL's to stay up to date:





What is the role of a tester in defect prevention and defect detection?

What is the role of testers in Defect Prevention and Defect Detection


Testers (especially beginners) often get confused with this Question - “What is the role of a tester in Defect Prevention and Defect Detection?”. In this post we will discuss the role of a tester in these phases and how to testers can prevent more defects in Defect Prevention phase and how testers can detect more bugs in Defect Detection phase. Here is the explanation about these questions.

Defect Prevention 

 

Defect prevention is mostly done by the developers. In the development phase, developers do activities like – code reviews/static code analysis, unit testing, etc. before committing the code in the code repositories. Testers are also involved in defect prevention by reviewing specification documents, the testers could try to find out any possible loop holes in the spec with which the developers are working on (Ideally this process is done by the QA’s and the senior members of the team), however this could done by the testers as well once the document is received by the testers. While studying specification documents, testers encounter various queries and many times with those queries, requirement document gets changed/updated.

Finding the defect in the spec plays a major role in addressing the issues before it is developed and it yields rewarding opportunities. Studying the specification document is an art, all the beginners and the less tenured people should learn to master this art.

Developers often neglect primary ambiguities in specification documents in order to complete the project on time; or they fail to identify them when they see them. Those ambiguities are then built into the code and represent a bug when compared to the end-user's needs. This is how testers help in defect prevention.

Defect Detection  


In Defect detection, role of a tester include implementing the most appropriate approach/strategy for testing, preparation/execution of test cases and conducting the necessary tests like - exploratory testing, functional testing, etc.

To increase the defect detection rate, tester should have complete understanding of the application. Ad hoc /exploratory testing should go in parallel with the test case execution as a lot of bugs can be found through these means.

Defect Prevention and Defect Detection







Join our community in Facebook and Google+ at the below URL's to stay up to date:







Rapid Software Testing

Rapid Software Testing.


Most of large organization in the world along with my company also have decided not to rely on pretense and 40 year-old ideas that were discredited 30 years ago. They are instead putting in place a system to recruit and grow highly skilled and highly motivated testers.

The companies are highly investing to identify and encourage testing champions who could become the role models and mentors for the rest of the group. Anyone may aspire to be in this special group, but to be recognized requires that the candidate tester demonstrate vigorous self-education and critical analysis. One of such demonstration has evolved the RST (Rapid Software Testing).

When this was implemented in my organisation some of the testers in the group began as strong skeptics of Rapid Testing. But the methodology is designed for skeptics– it is based on skill development and heuristics rather than pushing “best practices.” In Rapid Testing, the skilled tester is always in charge, not pieces of paper or officious charts.

RST requires each tester to employ his own judgment and technical analysis, much like what airlines expect of pilots, or hospitals expect of doctors. That can’t work on a large scale without a strong corporate commitment to training and personal ethics. Management must drive out fear, so that testers are willing to take the sort of risks that come from making their own decisions about test strategy. But the onus is on the testers to earn personal credibility within an internal community that can effectively police itself. Any tester, at any time, is expected to stand up and explain and defend his work.

Till now, I’m aware of only two large companies in the world that have made a commitment to this kind of professionalism, which is an altogether different sort of professionalism than the ceremonial certification variety that is promoted by most organizations. Such commitment has to be strongly supported by the top management, and I have personally witnessed when this was implemented in my mid size company only in my project, in my weeks of working with them, that the testers at had fire in their eyes. There are testers everyone in world who deserve to have an international reputation.

Rapid testing can be extended with the following activities to make sure the test results are properly aligned and useful to the client.

Analyze bug list

    Assess bug report quality
    Reproduce bugs
    Close duplicates and non-bugs
    Add labels and categorize according to risk
    What did the client know about before we started?
    What does the client consider important that we found?

Produce “official” test coverage outline
Produce “official” Risk List
Produce official sequence of events
Describe our test activities
Analyze test session reports
Describe what we did not test
Analyze tools used
Identify outstanding student work
Write report narrative and summary

In a real project, our reporting (other than the bug list itself) is either oral, or expressed in brief written statements. On a normal project, once we get organized (after a few days if it’s a new project) reporting gets pretty easy.



Join our community in Facebook and Google+ at the below URL's to stay up to date:

Easiest Automation Tool For iOS App Testing

Record and playback option for testing iOS app's


The long search for a tool to test the iOS applications with the easy record and playback option has paid me the reward. On my long search for easier way to test the mobile application, I came across this application. It offers a lot of sophisticated features. The name of the tool is ‘Test Studio for iOS’ (Mobile Testing Tool) is now available in App Store.

I have downloaded this App and experience was really good. If you are fed up with the regular mobile application testing and would like to explore new things then it’s time for you to give a try.

Here are some of the cool features which I observed in this application:

1. Record and run test
2. Test native, web and hybrid apps
3. Invite your colleagues as a beta tester for a project

Native app testing can be done after downloading the extension for native iOS app testing.

App Testing

Test Studio for iOS, supports testing of applications to all the iOS devices. I believe Test Studio for iOS is the easiest automated testing solution for iOS app testing and is downloadable from Apple’s App Store directly to customers’ devices.

Automate the Web testing

Record the test and play back with different set of test data. Update tests instead of re-record everything. Edit the values in the existing recorded steps and continue recording from a specific point in the test.

Ad-hoc Testing

I was rather surprised to see the option to use the ad-hoc testing as well to manually walk through an application and record feedback about the UI or bugs they encounter, and then send comments and screenshots directly to your email.


Just have a look at it, I hope most of you would love it. Thanks to the developers of solving much awaited option and helping the mobile application testers. Just have a look at their tour video:




Join our community in Facebook and Google+ at the below URL's to stay up to date:




Mobile App Testing Interview Questions

Some of the popular tech interview questions in mobile application testing


Here are some of the popular interview questions that were asked to my friends, colleagues and me while looking out for a job in Mobile Application Testing industry. I hope most of you would be interested in seeing what the interviewer looks for from a mobile application tester. Let all of us try and answer the questions which would be beneficial to all of us. If you came across any other questions, please feel free to post a comment in this blog so that everyone could get benefited out of it.


                 




  1. Difference between error, bug, defect, fault, failure?
  2. What is validation and verification?
  3. Explain Software test lifecycle?
  4. Explain buglife cycle?
  5. What is software Testing Methodologies?
  6. What is traceability matrix?
  7. What is performance testing?
  8. Different kind of testing performed in mobile application testing?
  9. What is the difference between simulator and emulator?
  10. What is the major difference between the android 2.2 and 3.2?
  11. What is the difference between native and hybrid applications?
  12. Have you used any automation tool to test the mobile application performance?
  13. How will you install application on Android sdk?
  14. How to do debug the Android application?
  15. How to identify the memory leaks in iOS application?
  16. What is network testing?
  17. What is Localization testing and how to perform localization testing of mobile applications?
  18. What is device ID?
  19. What are the differences between mobile application testing and web application testing?
  20. What is the difference between mobile handset testing and the mobile application testing?
  21. Is there any specific testing tool to test the Blackberry and Symbian Mobile applications?
  22. What is Interruption Testing and how to perform it?
  23. How to test the MMS application?
  24. Describe a real time scenario where android can be used?
  25. What is the screen size of iphone and ipad?
  26. What are the different Storage Methods in android?
  27. Write a program to show the addition and removing of the package in admin?
  28. Explain the pros and cons of using simulator and emulator for testing mobile application?
  29. How would you approach usability testing of mobile application?
  30. What are the challenges of mobile application testing and explain it in detail?
  31. What are the test scenarios for android mobile application?

Join our community in Facebook and Google+ at the below URL's to stay up to date:




Web Application Testing Checklist - Part 2


Web Application Testing Checklist


I hope you would find the Part 1 of the checklist pretty interesting. Please do share your comments if any. Here is the Part 2 of it.

 

APPLICATION SPECIFIC FUNCTIONAL REQUIREMENTS


1.   DATA INTEGRATION

  • Check the maximum field lengths to ensure that there are no truncated characters?
  • If numeric fields accept negative values can these be stored correctly on the database and does it make sense for the field to accept negative numbers?
  • If a particular set of data is saved to the database check that each value gets saved fully to the database. (i.e.) Beware of truncation (of strings) and rounding of numeric values.

2. DATE FIELD CHECKS

  • Assure that leap years are validated correctly & do not cause errors/miscalculations.
  • Assure that Feb. 28, 29, 30 are validated correctly & do not cause errors/ miscalculations.
  • Is copyright for all the sites includes Yahoo co-branded sites are updated

3. NUMERIC FIELDS

  • Assure that lowest and highest values are handled correctly.
  • Assure that numeric fields with a blank in position 1 are processed or reported as an error.
  • Assure that fields with a blank in the last position are processed or reported as an error an error.
  • Assure that both + and - values are correctly processed.
  • Assure that division by zero does not occur.
  • Include value zero in all calculations.
  • Assure that upper and lower values in ranges are handled correctly. (Using BVA)

2.4 ALPHANUMERIC FIELD CHECKS

  • Use blank and non-blank data.
  • Include lowest and highest values.
  • Include invalid characters & symbols.
  • Include valid characters.
  • Include data items with first position blank.
  • Include data items with last position blank.




INTERFACE AND ERROR HANDLING

1. SERVER INTERFACE

  • Verify that communication is done correctly, web server-application server, application server-database server and vice versa.
  • Compatibility of server software, hardware, network connections

2. EXTERNAL INTERFACE

  • Have all supported browsers been tested?
  • Have all error conditions related to external interfaces been tested when external application is unavailable or server inaccessible?

3. INTERNAL INTERFACE

  • If the site uses plug-ins, can the site still be used without them?
  • Can all linked documents be supported/opened on all platforms (i.e. can Microsoft Word be opened on Solaris)?
  • Are failures handled if there are errors in download?
  • Can users use copy/paste functionality? Does it allows in password/CVV/credit card no field?
  • Are you able to submit unencrypted form data?

4. INTERNAL INTERFACE

  • If the system does crash, are the re-start and recovery mechanisms efficient and reliable?
  • If we leave the site in the middle of a task does it cancel?
  • If we lose our Internet connection does the transaction cancel?
  • Does our solution handle browser crashes?
  • Does our solution handle network failures between Web site and application servers?
  • Have you implemented intelligent error handling (from disabling cookies, etc.)?



COMPATIBILITY


1. BROWSERS

  • Is the HTML version being used compatible with appropriate browser versions?
  • Do images display correctly with browsers under test?
  • Verify the fonts are usable on any of the browsers
  • Is Java Code/Scripts usable by the browsers under test?
  • Have you tested Animated GIFs across browsers?

2. VIDEO SETTINGS

  • Screen resolution (check that text and graphic alignment still work, font are readable etc.) like 1024 by 768, 600x800, 640 x 480 pixels etc
  • Color depth (256, 16-bit, 32-bit)

3 CONNECTION SPEED

  • Does the site load quickly enough in the viewer's browser within 8 Seconds?

4 PRINTERS

  • Text and image alignment
  • Colors of text, foreground and background
  • Scalability to fit paper size
  • Tables and borders
  • Do pages print legibly without cutting off text?




Please do share your comments about the blog and how it helped get a job or how it helped solved the challenges you faced so that everyone could learn and excel together.

Join our community in Facebook and Google+ at the below URL's to stay up to date:




Web Application Testing Checklist - Part 1

Basic Web Application Testing Checklist


In order to help the new testers and the tenured testers for a quick review of the application for its readiness, I have put in all the information, which ever I have created the collected information over a period of time. Please do share your comments if any.

USER INTERFACE

1. COLORS

  • Are hyperlink colors standard?
  • Are the field backgrounds the correct color?
  • Are the field prompts the correct color?
  • Are the screen and field colors adjusted correctly for non-editable mode?
  • Does the site use (approximately) standard link colors?
  • Are all the buttons are in standard format and size?
  • Is the general screen background the correct color?
  • Is the page background (color) distraction free?

2. CONTENT

  •  All fonts to be the same
  • Are all the screen prompts specified in the correct screen font?
  • Does content remain if you need to go back to a previous page, or if you move forward to another new page? (Note: This may be altered based on the application and the requirement)
  • Is all text properly aligned?
  • Is the text in all fields specified in the correct screen font?
  • Is all the heading are left aligned
  • Does the first letter of the second word appears in lowercase?

3. IMAGES

  • Are all graphics properly aligned?
  • Are graphics being used the most efficient use of file size?
  • Are graphics optimized for quick downloads?
  • Assure that command buttons are all of similar size and shape, and same font & font size.
  • Banner style & size & display exact same as existing windows
  • Does text wrap properly around pictures/graphics?
  • Is it visually consistent even without graphics?

4. INSTRUCTIONS

  • Is all the error message text spelt correctly on this screen?
  • Is all the micro-help text (i.e tool tip) spelt correctly on this screen?
  • Micro help text (i.e tool tip) for every enabled field & button
  • Progress messages on load of tabbed(active screens) screens

5. NAVIGATION

  • Are all disabled fields avoided in the TAB sequence?
  • Are all read-only fields avoided in the TAB sequence?
  • Can all screens accessible via buttons on this screen be accessed correctly?
  • Does a scrollbar appear if required?
  • Does the Tab Order specified on the screen go in sequence from Top Left to bottom right? This is the default unless otherwise specified.
  • Is there a link to home on every single page?
  • On open of tab focus will be on first editable field
  • When an error message occurs does the focus return to the field in error when the user cancels it?

6. USABILITY

  • Are all the field prompts spelt correctly?
  • Are fonts too large or too small to read?
  • Are names in command button & option box names are not abbreviations.
  • Assure that option boxes, option buttons, and command buttons are logically grouped together in clearly demarcated areas "Group Box"
  • Can the typical user run the system without frustration?
  • Do pages print legibly without cutting off text?
  • Does the site convey a clear sense of its intended audience?
  • Does the site have a consistent, clearly recognizable "look-&-feel"?
  • Does User cab Login Member Area with both UserName/Email ID?
  • Does the site look good on 640 x 480, 600x800 etc.?
  • Does the system provide or facilitate customer service? i.e. responsive, helpful, accurate?
  • Is all terminology understandable for all of the site’s intended users?

7. TEXT BOXES

  • Move mouse to textbox and it should be changed to insert bar for editable text field and should remain unchanged for non-editable text field.
  • Test overflowing textbox by inserting as many characters as you can in the text field. Also test width of the text field by entering all capital W.
  • Enter invalid characters, special characters and make sure that there is no abnormality.
  • User should be able to select text using Shift + arrow keys. Selection should be possible using mouse and double click should select entire text in the text box.

8. RADIO BUTTONS

  • Only one should be selected from the given option.
  • User should be able to select any button using mouse or key board
  • Arrow key should set/unset the radio buttons.

9. CHECK BOXES

  • User should be able to select any combination of checkboxes
  • Clicking mouse on the box should set/unset the checkbox.
  • Space bar should also do the same

10. PUSH BUTTONS

  • All buttons except OK/Cancel should have a letter access to them. This is indicated by a letter underlined in the button text.  The button should be activated by pressing ALT
  • Clicking each button with mouse should activate it and trigger required action.
  • Similarly, after giving focus SPACE or RETURN button should also do the same.
  • If there is any Cancel button on the screen, pressing Esc should activate it.

11. DROP DOWN LIST BOXES

  • Pressing the arrow should give list of options available to the user. List can be scrollable but user should not be able to type in.
  • Pressing Ctrl-F4 should open the list box.
  • Pressing a letter should bring the first item in the list starting with the same letter.
  • Items should be in alphabetical order in any list.
  • Selected item should be displayed on the list.
  • There should be only one blank space in the dropdown list.

12. COMBO BOX

  • Similar to the list mentioned above, but user should be able to enter text in it.

13. LIST BOXES

  • Should allow single select, either by mouse or arrow keys.
  • Pressing any letter should take you to the first element starting with that letter
  • If there are view/open button, double clicking on icon should be mapped to these behavior.
  • Make sure that all the data can be seen using scroll bar.

 



FUNCTIONALITY ASPECTS

1. LINKS

  • Check that the link takes you to the page it said it would.
  • Ensure to have no orphan pages (a page that has no links to it)
  • Check all of your links to other websites
  • Are all referenced web sites or email addresses hyperlinked?
  • If we have removed some of the pages from our own site, set up a custom 404 page that redirects your visitors to your home page (or a search page) when the user try to access a page that no longer exists.
  • Check all mailto links and whether it reaches properly

2. FORMS

  • Acceptance of invalid input
  • Optional versus mandatory fields
  • Input longer than field allows
  • Radio buttons
  • Default values on page load/reload(Also terms and conditions should be disabled)
  • Is Command Button can be used for Hyperlinks and Continue Links ?
  • Is all the data inside combo/list box are arranged in chronological order?
  • Are all of the parts of a table or form present? Correctly laid out? Can you confirm that selected texts are in the "right place?
  • Does a scrollbar appear if required?

3. DATA VERIFICATION AND VALIDATION

  • Is the Privacy Policy clearly defined and available for user access?
  • At no point of time the system should behave awkwardly when an invalid data is fed
  • Check to see what happens if a user deletes cookies while in site
  • Check to see what happens if a user deletes cookies after visiting a site

Click here to move on to the next part.


Please do share your comments about the blog and how it helped get a job or how it helped solved the challenges you faced so that everyone could learn and excel together.

Join our community in Facebook and Google+ at the below URL's to stay up to date:


 

Basic concept of localization testing


Basic concept of localization testing on mobile application.


Localization testing checks how well the build has been localized into a particular target language. For example, if a web/mobile application is built in English and if the company wants to use the same application in other languages like Hindi, Chinese, Japanese, etc. instead of creating the different application for different languages or regions. Then at this juncture localization testing comes into play. The developers would make the same application run on different languages. But with the localization process exceedingly difficult to verify, without knowing the native language of the region.  If the product is not globalized enough to support a given language then your application is regional and run and get popularity in target area. Localization testing requires both source and target language versions of the product installed on the environment that a typical user would use. Therefore attention must be paid to the correct version of the operating system, language, regional settings and more.

Most of them would get really confused with localization testing and the linguistic testing. Localization testing focuses only on the following parameters:

1) Correct functionality
2) Appearance
3) Completeness of the localized product.


whereas linguistic testing takes care of ensuring the correct language rules are being used and focuses on correct in-context linguistic usage.

Testing teams should pay attention to the tiniest details and differences. They should look for truncations, misalignment's, un-translated strings. The testers should also be noted that the localization bug differs from the core product bug. The localization bug is specific to the language under test and it may be specific to the group of languages. For example: Most of you would have noticed some websites offering country specific, however the content of the website would be the same but the language would change. Hence it is enough to regress once or twice because it is done by tester. But should be verified by technical writer or language expert. Tester can only compare the text and observe the truncation and overlap issue generally.

Three stages of Localization are given below:


Stage 1
: The product is not translated, but it must work on foreign language operating system.


Stage 2: The product user interface, release notes and installation guide only translated on targeted language.


Stage 3: The product user interface, online help, and printed documentations are translation



The following needs to be considered in localization testing:
• Upper and Lower case conversions (general rules for any language)
• Video Content (if implement).
• Keyboards is mandatory (pre defined key for app handling)
• Things that are often altered during localization, such as the User Interface and content files.
• Operating System (rex,android,iPhone OS)
• Text Filters if applicable (searching based on alphabet)
• Hot keys(before release the build)
• Spelling Rules (general rules for any language)
• Sorting Rules (general rules for searching and sorting)
• Date formats and currencies of country like dollar sign, pound and other format(special character).
• Rulers and Measurements(if implements)
• Memory Availability
• Local market complies with the local laws and regulations
• Help and about (how to install, play, mouse key function etc...) 



Learning some of the advanced concepts in the testing industry could make you eligible and choose your desired jobs. I'm a person who would always love to learn new technologies and concepts and would be sharing my experience in this blog.


Please do share your comments about the blog and how it helped get a job or how it helped solved the challenges you faced so that everyone could learn and excel together.


Join our community in Facebook and Google+ at the below URL's to stay up to date:


Facebook Page: http://www.facebook.com/SoftwareQaHelp
Google+ : https://plus.google.com/101680718973348361876