Test cases of pen are given below: -
But keep one thing in mind that test cases for pen may vary if you have different requirements or set of requirements.
Below is given different test cases of pen which does not contain any requirements or specifications?
Test cases of pen are like that:
1. Verify the color of the pen.
2. Check GUI testing means logo of the pen maker.
3. Check Usability testing means grip of the pen.
4. Verify whether the pen is ballpoint pen or ink pen.
5. Check Integration Testing means cap of the pen should easily fit beside the body of the pen.
6. Check pen should be continuously in writing mode.
2. Check GUI testing means logo of the pen maker.
3. Check Usability testing means grip of the pen.
4. Verify whether the pen is ballpoint pen or ink pen.
5. Check Integration Testing means cap of the pen should easily fit beside the body of the pen.
6. Check pen should be continuously in writing mode.
Some Functional test cases for pen:
1. Check whether it writes on paper or not.
2. Verify whether the ink on the paper is belongs with the similar color as what we see in the refill.
Performance and load test cases for pen:
1. Verify how it performs when writing on wet paper.
2. Verify how it performs when writing on rough paper.
3. Verify how it performs when writing on hand because we occasionally do that
4. Check load test means when pen is pressed very hard against the tough surface then pen refill should not come out of the pen.
Negative test cases about pen:
1. Verify whether ink is available or not.
2. Check if ink is available, than the pen does not write on the paper.
3. Verify by bend the refill at multiple ends and then try to write with it.
4. Verify by dip the pen always in to the water and then write it again.
5. Check whether it write on leaves or not.
Additional test cases for pen:
1. Check usability testing means test by writing on a section of paper, Examine if you can write smoothly. It should not be writing and stopping among (with) breaks.
2. Check capability or reliability testing means Test the writing capacity (the amount of writing that is possible from a single refill) of the pen.
3. Check Robustness testing means Test wherever you can carry the pen in to your shirt and pent pocket using its cap. The cap distension should be solid enough to grip your pocket.
4. Check Compatibility testing means Test by writing on distinct types of surfaces like: rough paper, packing material, glass, leather, cotton, wood, plastic, metals like aluminum or iron, polythene sheet etc.
Conclusion
At end we conclude that apart from above mentioned test cases there are numerous test cases for pen but these above mentioned are the universal one.
There are numerous test cases of fan which are given below:
Test case 1: Check whether it moves or not.
Description: Ensure that fan should moves properly.
Expected result: Fan should be moving.
Test case 2: Check it should have minimum 3 blades.
Description: Ensure that length of fan blades should be considered to 3 blades.
Expected result: Length of fan blades should not be shorter than 3 blades.
Test case 3: Check it should be on when electric button (switch) is on.
Description: Ensure that fan should start working when electric switch is on.
Expected result: Fan should be on when electric button (switch) is on.
Test case 4: Check whether Speed of the fan definitely be controlled by the regulator.
Description: Ensure that speed of fan should be controlled.
Expected result: Fan speed should be controlled by the regulator.
Test case 5: Check it should be stop working once the electric switch off.
Description: Ensure that fan should stop working once the electric switch is off.
Test case 6: Check the proper "company name" should be displayed on fan or not.
Description: Always ensure that name of company should be properly displayed on fan.
Expected result; Proper name of company should be displayed on fan.
Test case 7: Check Fan should always work in clock-wise direction.
Description: Ensure that direction of fan should be in clock-wise.
Expected result: Fan should work in clock-wise direction.
Test case 8: Check the color of the fan blades.
Description: Always ensure that all the blades of fan have same color.
Expected result: Color of all the blades of fan should be of same color.
Test case 9: Check the fan during (while) in motion should not vibrate.
Description: Ensure that the fan during (while) in motion should not vibrate.
Expected result: Fan should not vibrate.
Test case 10: Check whether the blades should have decent distance from the ceiling.
Description: Ensure that fan blades should have decent distance from the ceiling.
Expected result: Fan blades should have decent distance.
Test case 11: Check the size of the fan blades.
Description: Always ensure that all the blades of fan have same size.
Expected result: Size of all the blades of fan should be of same size.
Test case 12: Check whether it operates in low voltage.
Description: Ensure that fan should properly operate in low voltage.
Expected result: Fan should be properly operated on low voltage.
Test case 13: Check whether speed varies when regulator adjusted.
Description: Ensure that speed of fan varies when we adjust the regulator.
Expected result: Speed of fan varies while adjusting the regulator.
Conclusion:
At end we conclude that above mentioned test cases are not based on any requirements or specifications. These test cases are without specifications and requirements.
Positive Testing: - When tester test the application from positive point of mind than it is known as positive testing.
Testing the application with valid input and data is known as positive testing.
Positive testing: - A test which is designed to check that application is correctly working. Here the aim of tester is to pass affecting application, sometimes it is obviously called as clean testing, and that is "test to pass".
Negative Testing: - When tester test the application from negative point of mind than it is known as negative testing.
Testing the application always with invalid input and data is known as negative testing.
Considering example length of password defined in requirements is 6 to 20 characters, and whenever we check the application by giving alphanumeric characters on password field between 6 to 20 characters than it is positive testing, because we test the application with valid data/ input.
Example of negative testing is given below:
Considering example as we know phone no field does not accept the alphabets and special characters it obviously accepts numbers, but if we type alphabets and special characters on phone number field to check it accepts the alphabets and special characters or not than it is negative testing.
Conclusion: -
At end we conclude that tester has to perform both these testing simultaneously.
Testingis necessary to increase the quality of the project. Testing is most time consuming, but a crucial activity of a software project.
Testingis needed not always for improving product and project quality but also for improving company quality. Without testing company can't grow at the upper level.
It is vital to the success of new system. For making the project reliable and Error Free, the complete project and product must be tested in a systematic and organized way.
DEFINITION OF TESTING
Its a Risk reduction process and measurement of Quality.
WHY NEED OF TESTING
It is remarkably performed for one of the two reasons: -
1. Bug Detection
2. Improvement belonging to quality
Testingis needed not always for improving product and project quality but also for improving company quality. Without testing company can't grow at the upper level.
Testingis needed for almost all the organization which wants to grown up easily. Testing is needed for properly understand the fault errors in software during its development phases.
Testingis necessary in software development. It always ensures the users satisfaction and reliability of affecting software.
Below given the example which clears why testing is necessary: -
For Example if a company works on some long projects, and delivers those projects to the client without doing the proper testing, and after delivering the projects to client if client found some big bugs on the projects, than at that time it is the ashamed for company.
And obviously that client never comes back for having testing of their projects so it's harm to company and apart from loss company quality is also decreasing so testing is needed.
Conclusion: -
At last we conclude it's a fact that, when specific person starts checking commodity which is prepare by some other person, there are definitely 99% chances that checker and observer will discover some problem with the system. So it clears testing is needed.
Look and feel testing is not a usability testing. The testing of the appearance and GUI aspects of an application is referred as look and feel testing.
Example of look and feel testing is given below:-
Taking example: - A website may perfectly well be working in one particular environment but always not be effective in other environment. This variation in environment can broadly be divided in into three categories:
1) Display Settings: - Different websites give different look and feel on different monitor and display settings.
2) Browser Settings: - A browser is software that always grants you to use, browse, or stuff the internet. Not only different browsers affect the appearance (look and feel) of disparate websites, also the different versions of the same browser cause the differences.
Considering example, the DHTML page looks different in version 4 of Netscape as compared to version 6 of the same browser.
3) Operating Systems/Platforms: - Apart from different display settings and use of different browsers, websites also behave differently in different operating systems/platforms.
There are ranges of platforms available in the world, usually categorized in PC, Unix/Linux and Macintosh, which cause the difference in the appearance of websites.
Conclusion:-
Look and feel testing looks similar to usability testing but on reality it's not.
Incremental testing is a way of integration testing in which first you test each module of the software individually then continue testing by adding another module to it then another.
Its proper explanation is "An integration testing strategy in which you test subsystems in isolation, and then continue testing as you integrate more and more subsystems".
Its proper explanation is "An integration testing strategy in which you test subsystems in isolation, and then continue testing as you integrate more and more subsystems".
Incremental testing is partial testing of a sketchy product. The objective of incremental testing is to provide an earlier feedback to software developers.
Incremental testing: - A discipline approach of testing the interfaces between units tested programs as well as between system components.
Advantage of incremental testing:-
When you observe a trouble, you can discover the defect more fluently because you have a better idea in which subsystem to look.
There are two forms of incremental testing:-
1.Vertical incremental testing.
Under this there are two testing strategies
i) Top-down testing
You start by testing only the user network, with the underlying functionality simulated by stubs, then you work downwards, integrating lower and lower layers.
Begin testing from the top of the module hierarchy and always works down to the bottom using interior stubs to stimulate the lower interfacing modules or program. It tests the program of low level design. If low level design is not ready than it uses a dummy module called stub.
ii) Bottom-up testing
In this you start by testing the very lowest levels of the software using drivers, and then work upwards, as you integrate successive layers.
Begin testing from the bottom of the hierarchy and always works up to the top. It requires the development of driver module which provides the test input call the module or program being testing and display the test output. It tests the program of high level design. If high level design is not ready than it uses a dummy module called driver.
2. Horizontal Incremental Testing
2. Horizontal Incremental Testing
Conclusion:-
We use stubs in top-down and drivers in bottom-up. If both dummy variables Stub and Driver are presented in the testing process than it is known as Sandwich Incremental Testing.
Stubs are dummy modules that are always distinguish as "called programs", or you can say that is handle in integration testing (top down approach), it used when sub programs are under construction.
Stubs are considered as the dummy modules that always simulate the low level modules.
Drivers are also considered as the form of dummy modules which are always distinguished as "calling programs", that is handled in bottom up integration testing, it is only used when main programs are under construction.
Driversare considered as the dummy modules that always simulate the high level modules.
Example of Stubsand Drivers is given below:-
For Example we have 3 modules login, home, and user module. Login module is ready and need to test it, but we call functions from home and user (which is not ready). To test at a selective module we write a short dummy piece of a code which simulates home and user, which will return values for Login, this piece of dummy code is always called Stubs and it is used in a top down integration.
Considering the same Example above: If we have Home and User modules get ready and Login module is not ready, and we need to test Home and User modules Which return values from Login module, So to extract the values from Login module We write a Short Piece of Dummy code for login which returns value for home and user, So these pieces of code is always called Drivers and it is used in Bottom Up Integration
Conclusion:-
So it is fine from the above example that Stubs act "called" functions in top down integration. Drivers are "calling" Functions in bottom up integration.
Functional testing means testing the application against business requirements. Functional testing is executed using the functional specifications given by the client or by the design specifications according to use cases given by the design team. Role of functional testing is to validating the behavior of an application.
Functional testing falls in to two categories:
Functional testing is more important because it always verifies that your system is fixed for release. The functional tests define your working system in a useful manner. In functional testing tester has to validate the application to see that all specified requirements of the client whatever we have said in SRS or BRS have been incorporated or not.
Functional testing is always concentrating on customer requirements and whereas the Non-Functional testing is always concentrating on customer expectations.
Functional testing is always concentrating on customer requirements and whereas the Non-Functional testing is always concentrating on customer expectations.
Functional and Non Functional Test Cases
Functional test cases target business goals and non functional test cases target performance, resource utilization, usability, compatibility etc. Functional testing is a part of system testing.
Example of functional testing is explained below
Considering example if you are functionally testing a word processing application, a partial list of checks you would perform minimally includes creating, saving, editing, spell checking and printing documents.
Types of Functional Testing
Functional testing falls in to two categories:
1. Positive functional testing: - This testing carry exercising the application's functions with valid input and also verifying that the outputs are correct.
Example:-
Again continuing with the word processing example, a positive test for the printing function might be to print a document containing both text as well as graphics to a printer that is online, filled with paper and for which the correct drivers are installed.
2. Negative functional testing: - This testing involves exercising application functionality using a combination of invalid inputs, some unexpected operating conditions and by some other "out-of-bounds" scenarios.
Example:-
Again continuing with the word processing example, a negative test for the printing function might be to disconnect the printer from the computers while a document is printing.
What probably should happen in these scenarios are a plain-English error message displayed, informing the user what happened and instructing him/her on how to fix the problem.
Conclusion:
At last we conclude that in functional testing functionality of the module is tested and structure is not considered. It is performed, based on user's perspective. These tests ensure that the system does what users are expecting it to do.
This type of testing means testing the functionality example include input the proper data and checking the output as per the requirement documents.