1. Test uploading different types of image files (like .jpg, .png, .gif, .bmp, etc) and see if you could upload them.
2. Test uploading other files (like .exe, .dll, .mpg, .mov, .mp3, .wav, .rm, .doc etc) and see if It could break the uploading process.
3. Test with an image file with size other than the specified limit (the maximum allowed size was 500KB. So I had to try with 0 KB files, 1 MB image files, 5 MB files etc).
4. Try uploading a virus infected image file [You can use EICAR (European Institute of Computer Anti-virus Research) test files. These files are not actually viruses but behave as virus files] and see if the web server could detect the virus and stop the upload!
5. Test typing in a wrong path (like typing 'F:\ walpapers\aamir_khan_001.jpg', in place of a correct path 'F:\ wallpapers\aamir_khan_001.jpg'). Look at the wrong spelling of 'walpaper'). This can easily happen if a user is entering the path of the image file to be uploaded instead of browsing and selecting the image file. I had to see that the system was capable of detecting the wrong path name of the file.
6. Test cancelling an upload process and see what happens.
7. Test with a slower network speed and low system configuration.
8. Test While unplugging the internet connection while uploading.
9. Rename a images file with special characters and test by uploading it.
10. Test with corrupted image files (wrongly encrypted files).
11. Test by changing the file extension in browse field after selecting one image.
for Ex : Chnage jpeg into GIF
12. Test By closing the browser while uploading
Link for downloading virus affected files : http://www.eicar.org/anti_virus_test_file.htm
Showing posts with label testing. Show all posts
Showing posts with label testing. Show all posts
Thursday, February 19, 2009
Friday, January 30, 2009
What we will do in Manual Testing?
1. Understand the functionality of program
2. Prepare a test environment
3. Execute test case(s) manually
4. Verify the actual result
5. Record the result as Pass or Fail
6. Make a summary report of the Pass and Fail test cases
7. Publish the report
8. Record any new defects uncovered during the test case execution
2. Prepare a test environment
3. Execute test case(s) manually
4. Verify the actual result
5. Record the result as Pass or Fail
6. Make a summary report of the Pass and Fail test cases
7. Publish the report
8. Record any new defects uncovered during the test case execution
Flow of testing
Before testing any application we should follow some standard flow.
Generic Testing flow is as follows
1. Smoke Testing
2. Sanity Testing
3. Component testing
4. Integration testing
5. System testing
6. Acceptance testing
Smoke testing is originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke... We will be concentrating on Basic functionality of the product. It is also called as Build verification testing
In Sanity Testing we will be focusing on the major functionality or the functionality in detail. It is the subset of Regression testing
In Component Testing we will be testing module by module
In Integration testing one or more modules are combined and tested. Eg: In larger domains like Telecom, there will be many modules so we will be integrating the modules and will be testing
In System testing all the modules are combined and the whole application is tested
Acceptance testing will be done to ensure the confidence in the system and it is done mainly by the end users
Note:
The flow of testing varies depending on the organization
Generic Testing flow is as follows
1. Smoke Testing
2. Sanity Testing
3. Component testing
4. Integration testing
5. System testing
6. Acceptance testing
Smoke testing is originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke... We will be concentrating on Basic functionality of the product. It is also called as Build verification testing
In Sanity Testing we will be focusing on the major functionality or the functionality in detail. It is the subset of Regression testing
In Component Testing we will be testing module by module
In Integration testing one or more modules are combined and tested. Eg: In larger domains like Telecom, there will be many modules so we will be integrating the modules and will be testing
In System testing all the modules are combined and the whole application is tested
Acceptance testing will be done to ensure the confidence in the system and it is done mainly by the end users
Note:
The flow of testing varies depending on the organization
Basics of Software Testing
“Testing is a skill. While this may come as a surprise to some people, it is a simple fact”
Software Testing:
Software testing is the process of finding the defects as soon as possible and fixing them before delivering products to the client and also verify that the application meets the client’s requirement.
This increases the “Quality” of the product and decreases the “Risk”
Importance of Testing:
It Increases Customer satisfaction and the number of customers as well.
It Increases the Quality of the application.
It Increases the reputation of the organization.
Methods of Testing:
1) Manual Testing
2) Automation Testing
Levels of Testing:
1) Unit testing
2) Integration testing
3) System Testing
4) Acceptance testing
Types of Testing: (For Web Applications)
Unit Testing:
Done by Developers.
Functional Testing:
1) Sanity Testing
2) Smoke Testing
3) Component Testing
4) Integration Testing
5) Regression Testing
6) URL Testing
7) System Testing
8) Globalization and Localization Testing
Non-Functional Testing:
1) Load Testing
2) Performance Testing
3) Compatibility Testing
4) Installation Testing
5) Usability Testing
6) User Interface Testing
7) Security Testing
Software Testing:
Software testing is the process of finding the defects as soon as possible and fixing them before delivering products to the client and also verify that the application meets the client’s requirement.
This increases the “Quality” of the product and decreases the “Risk”
Importance of Testing:
It Increases Customer satisfaction and the number of customers as well.
It Increases the Quality of the application.
It Increases the reputation of the organization.
Methods of Testing:
1) Manual Testing
2) Automation Testing
Levels of Testing:
1) Unit testing
2) Integration testing
3) System Testing
4) Acceptance testing
Types of Testing: (For Web Applications)
Unit Testing:
Done by Developers.
Functional Testing:
1) Sanity Testing
2) Smoke Testing
3) Component Testing
4) Integration Testing
5) Regression Testing
6) URL Testing
7) System Testing
8) Globalization and Localization Testing
Non-Functional Testing:
1) Load Testing
2) Performance Testing
3) Compatibility Testing
4) Installation Testing
5) Usability Testing
6) User Interface Testing
7) Security Testing
Subscribe to:
Posts (Atom)