1) List down usecases (taken from business cases) from function specs For each use case write a test case and categorize them into sanity tests, functionality, GUI, performance etc Then for each test case, write its workflow 2) For a GUI application - make a list of all GUI controls For each control start writing test cases for testing of the control UI, functionality (impact on the whole application), negative testing (for incorrect inputs), performance etc
Correct Answer: Security/penetration testing is testing how well the system is protected against unauthorized internal or external access, or willful damage This type of testing usually requires sophisticated testing techniques
Correct Answer: Similar to system testing, the *macro* end of the test scale is testing a complete application in a situation that mimics real world use, such as interacting with a database, using network communication, or interacting with other hardware, application, or system
4. What are the different tests that can be done for Client Server Application and Web-based Application. Give details.
Correct Answer: For both client server and web based applications, the testing is the same except one thing: We test web based applications in different browsers, for example, Internet Explorer (will test in different versions like IE 50, IE 60, IE 70), Firefox, Safari (for Mac) and so on where as for client server, we don?t need to test in the browsers
5. How to write Regression test cases? What are the criteria?
Correct Answer: Regression test cases are also based on the requirement documents They are written more into detail and with every release (build), the testers need to do regression testing The criteria for regression testing are; there should be no major defects while we do our smoke test and functional testing
6. What is GUI testing? What elements will we cover in GUI testing?
Correct Answer: In GUI testing, need to cover the customer requirement if don't have to validate Font size, colors, spellings(labels) etc Every application should follow Microsoft rules like - Controls should be Initcap (ie every label should start with Capital letter )Can observe that in Win applications every label starts with Caps - OK or Cancel button should exist - Controls should not be overlapped - Controls should be alligned properly (left side alignment is mandatory but the right side is optional) - Controls should be visible - Short cut keys should be provided - System menu should exist (ie if u press Alt key + Space bar a menu will appear at the left most corner ) - Mouse pointer events Colors, Label Names, Tab Order, Alignment, graphs , Navigation of the software to test in GUI Testing
Correct Answer: 1) List down usecases (taken from business cases) from function specs For each use case write a test case and categorize them into sanity tests, functionality, GUI, performance etc Then for each test case, write its workflow 2) For a GUI application - make a list of all GUI controls For each control start writing test cases for testing of the control UI, functionality (impact on the whole application), negative testing (for incorrect inputs), performance etc
Correct Answer: Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification
9. What is the proper way of setting up an Android-powered device for app development?
Correct Answer: The following are steps to be followed prior to actual application development in an Android-powered device: - Declare your application as ?debuggable? in your Android Manifest - Turn on ?USB Debugging? on your device - Set up your system to detect your device
Correct Answer: The Google Android SDK is a toolset that developers need in order to write apps on Android enabled devices It contains a graphical interface that emulates an Android driven handheld environment, allowing them to test and debug their codes