Interview Questions
-- Why can’t constructors be final, static or abstract in Java?
- When you set a method as final, it means: You don’t want any class override it”, but constructor by JLS definition can’t overridden,so it is clean.
- When you set a method as ‘abstract’,it means:”Method don’t have any body and you want to implement it at another time in a child class”, but the constructor is called implicitly when the new keyword is used so it can’t lack a body.
- When you set a method as ‘static’, it means: “Method belong to class, not a particular object” but constructor implicitly called to initialize an object, so there is no purpose in having a static constructor.
-- Difference Between Verification And Validation With Example?
- Verification
1- Are we building the system right?
2- Verification is the process of evaluating products in a development phase to find out whether they meets the specified requirements.
3- The objective of Verification is to make sure that the product being develop is as per the requirements and design specifications.
4- Following activities are involved in Verification: Reviews, Meetings and Inspections.
5- Verification is carried out by QA team to check whether implementation software is as per specification document or not.
6- Execution of code is not comes under Verification.
7- Verification process explains whether the outputs are according to inputs or not.
8- Verification is carried out before the Validation.
9- Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc.
Following items are evaluated during Verification: Plans, Requirement Specifications, Design Specifications, Code, Test Cases etc,
10- It is basically manually checking the of documents and files like requirement specifications etc.
Validation:
1- Are we building the right system?
2- Validation is the process of evaluating software at the end of the development process to determine whether software meets the customer expectations and requirements.
3- The objective of Validation is to make sure that the product actually meet up the user’s requirements, and check whether the specifications were correct in the first place.
4- Following activities are involved in Validation: Testing like black box testing, white box testing, gray box testing etc.
5- Validation is carried out by testing team.
6- Execution of code is comes under Validation.
7- Validation process describes whether the software is accepted by the user or not.
8- Validation activity is carried out just after the Verification.
9- Following item is evaluated during Validation: Actual product or Software under test.
Validation uses methods like black box (functional) testing, gray box testing, and white box (structural) testing etc.
10- It is basically checking of developed program based on the requirement specifications documents & files.
Software Bug Life Cycle:
- New
|
Assign
| | Rejected
---------> Open -------> | Duplicate
| | | Deffered
| | | Not a Bug
| Fixed
ReOpen |
| Pending Retest
| |
<---------Retest
| (if verified)
Closed
SOFTWARE QUALITY CONTROL Fundamentals:
- Software Quality Control (SQC) is a set of activities for ensuring quality in software products.
It includes the following activities:
Reviews
- Requirement Review
- Design Review
- Code Review
- Deployment Plan Review
- Test Plan Review
- Test Cases Review
Testing
- Unit Testing
- Integration Testing
- System Testing
- Acceptance Testing
- Software Quality Control is limited to the Review/Testing phases of the Software Development Life Cycle and the goal is to ensure that the products meet specifications/requirements.
- The process of Software Quality Control (SQC) is governed by Software Quality Assurance (SQA). While SQA is oriented towards prevention, SQC is oriented towards detection. Read Differences between Software Quality Assurance and Software Quality Control.
Some people assume that QC means just Testing and fail to consider Reviews; this should be discouraged.
Software Quality Assurance:
- Software Quality Assurance (SQA) is a set of activities for ensuring quality in software engineering processes (that ultimately result in quality in software products).
It includes the following activities:
- Process definition and implementation
- Auditing
- Training
Processes could be:
- Software Development Methodology
- Project Management
- Configuration Management
- Requirements Development/Management
- Estimation
- Software Design
- Testing
Once the processes have been defined and implemented, Quality Assurance has the following responsibilities:
identify weaknesses in the processes
correct those weaknesses to continually improve the process
The quality management system under which the software system is created is normally based on one or more of the following models/standards:
CMMI
Six Sigma
ISO 9000
Note: There are many other models/standards for quality management but the ones mentioned above are the most popular.
Software Quality Assurance encompasses the entire software development life cycle and the goal is to ensure that the development and/or maintenance processes are continuously improved to produce products that meet specifications/requirements.
The process of Software Quality Control (SQC) is also governed by Software Quality Assurance (SQA).
SQA is generally shortened to just QA.
Quality Assurance Quality Control
It is a process which deliberate on providing assurance that quality request will be achieved. QC is a process which deliberates on fulfilling the quality request.
A QA aim is to prevent the defect.
QA is the technique of managing the quality. QC is method to verify the quality.
QA does not involve executing the program. QC always involves executing the program.
All team members are responsible for QA. Testing team is responsible for QC.
QA e.g. Verification. QC e.g. Validation.
QA means Planning for doing a process. QC Means Action for executing the planned process.
Statistical Technique used on QA is known as Statistical Process Control (SPC.) Statistical Technique used on QC is known as Statistical Quality Control (SPC.)
QA makes sure you are doing the right things. QC makes sure the results of what you’ve done are what you expected.
QA Defines standards and methodologies to followed in order to meet the customer requirements. QC ensures that the standards are followed while working on the product.
QA is the process to create the deliverables. QC is the process to verify that deliverables.
QA is responsible for full software development life cycle. QC is responsible for software testing life cycle.
Key Points
In QA, processes are planned to evade the defects.
QC agreements with discovery the defects and modifying them while making the product.
QA detects weakness.
QC detects defects.
Quality Control | Quality Assurance
----------------------------------------------------------------------------------------------
1- QC is a process which deliberates on fulfilling | 1- It is a process which deliberate on providing
the quality request. | assurance that quality request will be achieved
2- A QC aim is to identify and improve the defects. | 2- A QA aim is to prevent the defect.
3- QC is method to verify the quality. | 3- QA is the technique of managing the quality.
4- QC always involve executing the program. | 4- QC does not involves executing the program.
5- Testing team is responsible for QC. | 5- All team members are responsible for QA.
6- QC is the process to verify that deliverables. | 6- QA is the process to create the deliverables
7- QC is product oriented. | 7- QA is process oriented.
8- QA is failure detection system. | 8- QA aim is to identify and Prevention of the defects.
|
|
|
Assurance (SQA), Software Quality Control (SQC) and Software Testing. Although they are interrelated and at some level they can be considered as the same activities, but there is indeed a difference between them.
Software Quality Assurance (SQA) is a process that ensures that developed software meets and complies with defined or standardized quality specifications.
Characteristics:
activities which ensure the implementation of processes, procedures and standards in context to verification of developed software and intended requirements;
focuses on processes and procedures rather then conducting actual testing on the software;
process oriented activities;
preventive activities; and
Quality Assurance (QA) is a subset of Software Test Life Cycle (STLC).
Software Quality Control (SQC) is limited to the Review/Testing phases of the Software Development Life Cycle and the goal is to ensure that the software meet specifications/requirements. The process of SQC is governed by SQA. While SQA is oriented towards prevention, SQC is oriented towards detection.
Characteristics:
activities which ensure the verification of developed software with respect to documented (or not in some cases) requirements;
focuses on actual testing by executing software with intend to identify defect through implementation of procedures and process;
product oriented activities;
corrective activities; and
Quality Control (QC) can be considered as the subset of Quality Assurance (QA).
Software Testing involves the execution of a software to evaluate one or more properties of interest with the intent of finding the defects.
Characteristics:
activities which ensure the identification of defects in the software;
focuses on actual testing;
product oriented activities;
reactive activities;
testing is the subset of Quality Control (QC).
What is TestCases?
- A test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly.
- A test case is a document, which has a set of test data, preconditions, expected results and postconditions, developed for a particular test scenario in order to verify compliance against a specific requirement.
- The process of developing test cases can also help find problems in the requirements or design of an application.
Test case tesmplete:
1- Test Case ID: The ID of the test case.
2- Test Case Name: Test case name or title.
3- Test Suite ID: The ID of the test suite to which this test case belongs.
4- Test Case Summary: The summary / objective of the test case.
5- Test Case Design By: The name of the author of the test case.
6- Test Case Design Date: The creation date of the test case.
7- Test Case Excecuted By: The name of the person who executed the test.
8- Test Case Excecution Date: The date of execution of the test.
9- Prerequisites: Any prerequisites or preconditions that must be fulfilled prior to executing the test.
10- Dependencies: Any dependency of test case to another test case.
11- Priority: Set the test case priority based on priority & saverity.
12- Related Requirement: The ID of the requirement this test case relates/traces to.
13- Test Data: The test data, or links to the test data, that are to be used while conducting the test.
14- Test Procedure(Steps): Step-by-step procedure to execute the test.
15- Expected Result: The expected result of the test.
16- Actual Result: The actual result of the test; to be filled after executing the test.
17- Status: Pass or Fail. Other statuses can be ‘Not Executed’ if testing is not performed and ‘Blocked’ if testing is blocked.
18- Remarks/Notes: Any comments on the test case or test execution.
19- Post Conditions: Post conditions for test case after test case excecution.
20- Test Environment: The environment (Hardware/Software/Network) in which the test was executed.
-------------------------------------------------------------------------------------------------------------------------------------------------------
--Final, finally and finalize in java
1) Final is used to apply restrictions on class, method and variable. Final class can't be inherited, final method can't be overridden and final variable value can't be changed.
Finally is used to place important code, it will be executed whether exception is handled or not.
Finalize is used to perform clean up processing just before object is garbage collected.
2) Final is a keyword.
Finally is a block.
Finalize is a method.
Important points on final in Java:
1) A constructor cannot be declared as final.
3) If method parameters are declared final then the value of these parameters cannot be changed.
4) It is a good practice to name final variable in all CAPS.
1. Final keyword can be applied to member variable, local variable, method or class in Java.
2. Final member variable must be initialized at the time of declaration or inside constructor, failure to do so will result in compilation error.
3. You can not reassign value to final variable in Java.
4. Local final variable must be initializing during declaration.
5. Only final variable is accessible inside anonymous class in Java.
6. Final method can not be overridden in Java.
7. Final class can not be inheritable in Java.
8. Final is different than finally keyword which is used on Exception handling in Java.
9. Final should not be confused with finalize() method which is declared in object class and called before an object is garbage collected by JVM.
10. All variable declared inside java interface are implicitly final.
11. Final and abstract are two opposite keyword and a final class can not be abstract in java.
12. Final methods are bonded during compile time also called static binding.
13. Final variables which is not initialized during declaration are called blank final variable and must be initialized on all constructor either explicitly or by calling this(). Failure to do so compiler will complain as "final variable (name) might not be initialized".
14. Making a class, method or variable final in Java helps to improve performance because JVM gets an opportunity to make assumption and optimization.
15. As per Java code convention final variables are treated as constant and written in all Caps e.g.
private final int COUNT=10;
16. Making a collection reference variable final means only reference can not be changed but you can add, remove or change object inside collection. For example:
Read more: http://javarevisited.blogspot.com/2011/12/final-variable-method-class-java.html#ixzz4QO4GSFEb
- Final Keyword In Java
Final is a keyword.
The final keyword in java is used to restrict the user. The java final keyword can be used in many context. Final can be:
variable
method
class
- if final used before variables then its become constant e.i. its value can't be change in program.
class Bike9{
final int speedlimit=90;//final variable
void run(){
speedlimit=400;
}
public static void main(String args[]){
Bike9 obj=new Bike9();
obj.run();
}
}//end of class
output: compile time error.
- if final used before methond then it can't be overridden by other methods but its inherited.
- if final used before class then it can't be inherited by other class.
- if final used before parameter then its become read only parameter for program.
- Blank final variable:
- The final keyword can be applied with the variables, a final variable that have no value it is called blank final variable or uninitialized final variable. It can be initialized in the constructor only.
- The blank final variable can be static also which will be initialized in the static block only.
- Q) Is final method inherited?
Ans) Yes, final method is inherited but you cannot override it. For Example:
class Bike{
final void run(){System.out.println("running...");}
}
class Honda2 extends Bike{
public static void main(String args[]){
new Honda2().run();
}
}
Output:running...
-- Q) What is blank or uninitialized final variable?
A final variable that is not initialized at the time of declaration is known as blank final variable.
If you want to create a variable that is initialized at the time of creating object and once initialized may not be changed, it is useful. For example PAN CARD number of an employee.
It can be initialized only in constructor.
-- Q) Can we initialize blank final variable?
Yes, but only in constructor. For example:
We must initialize the blank final variable in constructor of the class otherwise it will throw a compilation error (Error: variable MAX_VALUE might not have been initialized).
class Bike10{
final int speedlimit;//blank final variable
Bike10(){
speedlimit=70;
System.out.println(speedlimit);
}
public static void main(String args[]){
new Bike10();
}
}
Output:70
- Q) Whats the use of blank final variable?
Lets say we have a Student class which is having a field called Roll No. Since Roll No should not be changed once the student is registered, we can declare it as a final variable in a class but we cannot initialize roll no in advance for all the students(otherwise all students would be having same roll no). In such case we can declare roll no variable as blank final and we initialize this value during object creation like this:
class StudentData{
//Blank final variable
final int ROLL_NO;
StudentData(int rnum){
//It must be initialized in constructor
ROLL_NO=rnum;
}
void myMethod(){
System.out.println("Roll no is:"+ROLL_NO);
}
public static void main(String args[]){
StudentData obj=new StudentData(1234);
obj.myMethod();
}
}
Output:
Roll no is:1234
-- Q) Uninitialized static final variable
A static final variable that is not initialized during declaration can only be initialized in static block. Example:
class Example{
//static blank final variable
static final int ROLL_NO;
static{
ROLL_NO=1230;
}
public static void main(String args[]){
System.out.println(Example.ROLL_NO);
}
}
Output: 1230
-- Q) What is final parameter?
If you declare any parameter as final, you cannot change the value of it.
class Bike11{
int cube(final int n){
n=n+2;//can't be changed as n is final
n*n*n;
}
public static void main(String args[]){
Bike11 b=new Bike11();
b.cube(5);
}
}
Test it Now
Output:Compile Time Error
-- Q) Can we declare a constructor final?
No, because constructor is never inherited.
- Finally:
- Rule: For each try block there can be zero or more catch blocks, but only one finally block.
- Note: The finally block will not be executed if program exits(either by calling System.exit() or by causing a fatal error that causes the process to abort).
-- Finally block in java can be used to put "cleanup" code such as closing a file, closing connection etc.
- Java finally block is a block that is used to execute important code such as closing connection, stream etc.
- Java finally block is always executed whether exception is handled or not.
- Java finally block follows try or catch block.
- Case 1
Let's see the java finally example where exception doesn't occur.
class TestFinallyBlock{
public static void main(String args[]){
try{
int data=25/5;
System.out.println(data);
}
catch(NullPointerException e){System.out.println(e);}
finally{System.out.println("finally block is always executed");}
System.out.println("rest of the code...");
}
}
Output:5
finally block is always executed
rest of the code...
- Case 2
Let's see the java finally example where exception occurs and not handled.
class TestFinallyBlock1{
public static void main(String args[]){
try{
int data=25/0;
System.out.println(data);
}
catch(NullPointerException e){System.out.println(e);}
finally{System.out.println("finally block is always executed");}
System.out.println("rest of the code...");
}
}
Output:finally block is always executed
Exception in thread main java.lang.ArithmeticException:/ by zero
- Case 3
Let's see the java finally example where exception occurs and handled.
public class TestFinallyBlock2{
public static void main(String args[]){
try{
int data=25/0;
System.out.println(data);
}
catch(ArithmeticException e){System.out.println(e);}
finally{System.out.println("finally block is always executed");}
System.out.println("rest of the code...");
}
}
Output:Exception in thread main java.lang.ArithmeticException:/ by zero
finally block is always executed
rest of the code...
- Finalize:
- It is a method present in a class which is called before any of its object is reclaimed by the garbage collector.finalize() method is used for performing code clean-up before the object is reclaimed by the garbage collector.
Java finalize example
class FinalizeExample{
public void finalize(){System.out.println("finalize called");}
public static void main(String[] args){
FinalizeExample f1=new FinalizeExample();
FinalizeExample f2=new FinalizeExample();
f1=null;
f2=null;
System.gc();
}
}
Generic Test case will be :
A) For Submit Button.
1) Check Whether Button is enable or not.
2) On Click Submit Button Data on Form should hit either DB or Redirect to other page based on requirement.
3) On clicking Submit button Data in the Form should not get reset or cancelled.
B) For Reset Button
1) Check Whether Button is enable or not.
2) On Click Reset Button Data on Form should not hit data into DB and it should not navigate to another page.
3) On clicking Reset button Data in the Form should get Cleared.
C) For Delete button
1) Check Whether Button is enable or not.
2) On Click Delete Button Data on Form should not insert data into DB and it should navigate from current page.
• Test cases/scenarios for Links – There are two types of link can be available on web page that is internal and external links here are some test scenarios to test link on web page
a. Tool tips text should be available and meaningful.
b. Check whether all external links are opening in new window with proper URL
c. Test all internal links are navigating within application as per requirement
d. Test links jumping on the same pages
e. Check whether email address link opening the mail instance like outlook
f. Test to check if there are any blank page to link
g. Test Links opening in other tab /window as per requirement
h. Compatibility Testing for all links on other browsers
i. Ensure that color of links change after the page is visited once. (This can vary as per the design).
j. Ensure that the link color is as per the specification.
k. Ensure that a hand icon is displayed when mouse pointer is hovered over the link.
l. Check loading time for internal links as per requirement
m. Check whether shared link is getting shared properly with correct address
n. Check whether shared link is getting opened properly
• Test cases/scenarios for Forms– There are various types of form one can find on webpages, but fields are relatively same, according to which following are the scenarios to test the form
a. Test the form position on the web page
b. Check whether all controls are available on the form as per requirement
c. Check the alignment of web controls in the form
d. Test all labels of the forms
e. An asterisk is displayed near required fields
f. Check the behavior of form by not filling up any data into the form.
g. Check heading of the form
h. Check phone number field with alphabetic data and with invalid formats
i. Check email field with invalid email format
j. Check Captcha field with reset button
k. Save and cancel buttons in the form
l. Check the behavior of form by adding random data in the text field.
m. Validation message on required field or incorrect values
n. Check whether the navigation between the fields is successful using tab
o. Multiple clicks on the submit should not be allowed while the registration is in progress.
p. Submit button can be disabled before entering the mandatory fields in the form.
• Test cases/scenarios for Search box– Search box is the common and most essential field of any website here are some scenarios which may help to test the search box field.
a. Without entering anything click on Search button.
b. Check the cross or cancel option to clear the search keyword
c. Click in the search field and press Enter key.
d. Enter any one character and click on Search button/press Enter key.
e. Enter only special characters and click on Search button.
f. Enter only numbers and click on Search button
g. Enter alphanumeric characters and click on Search button
h. Enter alphanumeric characters and special characters and click on search button.
i. Enter string more than the max char limit of the field.
j. Enter string with spaces (before string, after string and in between) and verify the results.
k. Verify this on all pages where Search box is available
l. Try to drag and drop image or other file in search box and check the result
m. Check if search is applied on water mark updated in search box
n. Check whether auto suggestion is working or not
• Test cases/scenarios for Result grid/Search result – Result grid is page displayed after user searched for particular keyword so while testing result grid following points may help tester
a. Enter the search criteria in Search field which will give only one result and verify the UI of the page
b. Enter the search criteria in search field which will not give any results and Verify the UI.
c. Enter First / middle/ last word of any title and verify the search results
d. For each item category -Enter the value in search field based on the above prepared “Test Data” and verify the search results.
e. For each category- Enter the value in search field which will give multiple results :
-Verify the UI and pagination.
-Verify sorting order of search results.
–Validate the search results and no. of Search results from the database
f. For each category-Add new item in the system and after that search the same item through the Search field.
g. For each category-Update title of any existing item and after that search updated item through the Search field with old and new title.
h. For each category-Remove any existing item from the system and after that search same item through the Search field.
i. Verify the above scenarios for logged in and not logged in user.
j. Verify that users are able to search public items only. They should not be able to search those items /details which are private
k. Check the total number of results to be displayed in one page
l. Duplicate records should not display in result
m. Pagination should be enabled when there are more results than the default result count per page
n. Check the number of result appears on a page it should be same on all pages till last page
o. Searched keyword should be highlighted in the search results page and also in the page where the keyword exists.
p. Proper messages should be displayed when there are no results.
q. Check the count of the search results displayed in the page.
• Test cases/scenarios for Text boxes and text area– Test area are most common field of web page and important too as maximum input like customer’s information ph. no. name, email ids are entered in text box and text can be entered from text boxes in free way so while testing text boxes or text areas testers should be more alert here are some scenarios to check the same
a. Check for the alpha characters or alpha numeric characters
b. Check for alphabet is accepted in upper and lower case both
c. Check the mandatory condition for the textbox if given
d. Check the textbox is blank or not by default
e. Check Max-Min character limit of text box
f. Check for numeric characters only
g. Check with the requirement whether it will accept numeric and special characters
h. Check by entering ”HTML tag” and click save button
i. Check by entering “Java Script” and click save button
j. Check by entering “Spaces” in the prefix and suffix of the entered character-Trimming of space
k. Check by entering “single quotes and double quotes”
l. Check Copy and Paste long texts from word or notepad
m. Check the height and alignment of text boxes are same throughout the site
n. Check drag and drop image in text box
o. Check text box except only spaces as input
p. Check the zip code text field with string instead of numbers.
q. Check the zip code text field with numbers shorter than required.
• Test cases/scenarios for Buttons– Buttons are another important field in web application as user feedback, customer information etc. will got saved or submitted only when is click on save or submit button. There are various types of buttons may have on web page following are some of them
a. Test cases/scenarios For Radio Buttons
Check for selecting a radio button
Check for only one radio button is getting selected at a time
Check for the Radio button label description
Check for size and color of button
Check for the alignment of the Radio Buttons
b. Test cases/scenarios for check box-
Check for selection of check box/s
Check for the Check Box label description
Check for the alignment of the Check Boxes
Check for height, length and width of each box
Check user can check multiple boxes at a time
Check the checked box is ticked
Check the unchecked box is unticked
Check if the checkbox selection enables the specific element
c. Test cases/scenarios For command buttons (Add/edit/delete)
Check the font size
Check the font color
Check the spelling mistake
Check the button size
Check whether expected result is displayed on click
Check when u have click the add button, record should be added.
Check when u have click the delete button, record should be deleted.
Check the value get modified when click on edit/update button
• Test cases/scenarios for Password – Password is critical field of all as it maintain user data safe so while testing password field tester should be more alert.
Check whether password field is accepting only characters as per requirement
Check for a password length
Check for password is displayed in encrypted format
Check for all possible combination of alphabets, numbers and special characters as per requirement
Check whether validation is placed if user fail to enter the correct password
• Test cases/scenarios for Email – Email is important part of website as it connect user and owner here are some points to check while testing email functionality
a. Check from Which id it will get fired
b. Check by whom it will received
c. Check Subject line of an Email
d. Check Content Of an Email
e. Check is there any link Present in Email if yes where it is redirecting.
f. Check repetitive click on same link results in?
g. Check the Spellings all over the Email
h. Check If mail is of “Do not Reply” Kind what happen even if replied
i. Check if mail is not of “Do not Reply” kind what will happen On reply
j. Check for special characters in email body template should be handled properly.
k. Check content of the email
l. Check email in different email services like outlook, Gmail, Hotmail, yahoo etc.
m. Check send email functionality using TO, CC and BCC fields
n. Check validation while sending blank mail content
o. Check validation while sender or receiver section is blank
p. Check sending high volume of emails.
q. Check various languages handled properly in content
r. Check whether email is not going to spam folder
• Test cases/scenarios for Image/file upload– It is very convenient for user to upload file or image rather than writing long paragraph so it should be user friendly and properly guided.
a. Check for uploaded image path
b. Check image upload and change functionality
c. Check image upload functionality with image files of different extensions (e.g. JPEG, PNG, BMP etc.)
d. Check image upload functionality with images having space or any other allowed special character in file name
e. Check duplicate name image upload
f. Check image upload with image size greater than the max allowed size. Proper error message should be displayed.
g. Check image upload functionality with file types other than images (e.g. txt, doc, pdf, exe etc.). Check validation for invalid format
h. Check if images of specified height and width (if defined) are accepted otherwise rejected
i. Check progress bar should appear for large size images
j. Check if cancel button functionality is working in between upload process
k. Check if file selection dialog shows only supported files listed
l. Check multiple images upload functionality
m. Check image quality after upload. Image quality should not be changed after upload
n. Check if user is able to use/view the uploaded images
• Test cases/scenarios for Dropdown filter– To avoid wrong inputs from user dropdown is best option or to fetch the correct data from many option available on the website. Below are some scenarios while testing
a. Check default selected value in dropdown
b. Check maximum character length display in the dropdown
c. Check maximum no. of values display in dropdown without scroll bar
d. Check dropdown should be open by clicking on both box and dropdown arrow
e. Check once dropdown is selected, you should be able to select values by keyboard arrow keys or mouse scroll even if dropdown is closed.
f. Check after selecting dropdown, if you press any alphabet key, the respective value should be selected automatically.
g. Check if user should not able to edit the dropdown value
h. Check whether dropdown values are arranged in alphabetical order
• Test cases/scenarios for Date field/Calendar control – Date field are frequently used field in most of the sites to test this field some points are suggested below
a. Check by entering the invalid date and valid month and valid year
b. Check by entering the valid date and valid month and invalid year
c. Check by entering the valid date and invalid month and valid year
d. Check by entering the valid date and invalid month and invalid year
e. Check by entering the invalid date and invalid month and invalid year
f. Check by entering the invalid date and valid month and invalid year
g. Check by entering the invalid blank space and valid month invalid
h. blank space
i. Check by entering the blank space for day and blank space for month and
j. blank space for year
k. Check whether the year entered is leap or ordinary year.
l. Check for ordinary year the max limit of number in day field in the month should be 31.
m. Check for leap year the max limit of number in day field in the month Feb should be 29.
n. Check alternate months for date in day field i.e. 30/31 should be accepted.
o. Check by entering the date below/beyond the range, i.e. 32 or 0 etc.
p. Check by entering the month below/beyond the range, i.e. 13 or 0…
q. Check by entering zero before the single digit number in date/month.
r. Check if auto populated calendar filed is open on click of box or on calendar icon
s. Check whether we should be able to select the desired day on the calendar.
t. Check after we click on to the selected date should come in to the box and calendar
u. Check if the calendar field is editable even if user can select date form calendar populated
v. Check editable calendar can take date format specified and not any other value
w. Check whether calendar control is opening in all the browsers
• Test cases/scenarios for Messages and pop up – Messages are guidance or alert for user so it is very necessary at every point messages should be given for user
a. Check Message For Each field of an web app
b. Check informative message should display standard icon, message content, cross and ok button
c. Check all text messages for spelling and grammar
d. Confirmation Messages
e. Pop up Messages
f. Messages as per Browser
g. Error Messages
h. Alert/Error message should be shown in red color
i. Check all alert messages should display question mark
j. Confirmation message of Successful Functionality Should be shown in Green color
k. Confirmation Before Delete functionality
l. Font, Alignment, Size and color of the Messages
m. Placing & Spacing Of Messages
n. Format of messages
o. Spellings of messages
p. While Message Pop up or a child window opens for message other areas will get Non editable.
q. Most important Message Should be easily understandable
r. Time must be Such as the message can be read by User
s. Messages must be related to concern page only it should get disappear once on new page
• Test cases/scenarios for Graphical Reports- Reports are analytical part so it should be properly represented and easy to understand
a. Check reports will get generated for respective data
b. Check the data must be reflect same as input given
c. Check in change in inputs immediate effect will update in reports on Refresh
d. Check the input with Special characters and effect in reports
e. Check Long text as input and then check the report
f. Check for different Formats of reports
g. Check label of X and Y axes are correct
h. Check legends are specified on reports
i. Check legends are easy to understand
