Vettanna provides software testers for all your testing needs.
Vettanna testers can:
· Supplement your existing test team with tester's of any skill level
· Setup your test team
· Manage your test team
· Write test cases
· Plan the test effort
· Automate your testing
· Conduct White Box testing
Conduct performance and load testing
· Test your foreign language versions
· Identify and improve your internal processes
Contact Vettanna today for a proposal to help you with your testing needs. 1-866-422-0948
Here are some of the types of testing that Vettanna can do for you:
| Acceptance Testing |
This is testing the product to known requirements or standards and verifying that the product is acceptable for the client. |
| Automated Testing |
Testers write code using an automation tool to make the test cases run automatically. For example, a web site has many links and during the life of the site many new pages will be added and some renamed. It is very time consuming and tedious for a person to click on all the links to verify that they all work and go to the correct page. But an automated test case can do it in a matter of minutes. This frees up your tester to test other more important features. |
| Error Conditions |
Does it fail gracefully when an error occurs and give the user an indication of what went wrong and what the user can do to remedy it? |
| Functionality |
Does is work as intended under normal, expected conditions? |
| GUI |
Is the user interface visually appealing, intuitive and effective? |
Limit testing/
Boundary testing |
Some people still use these words individually. We classify limits and boundaries as test data that Vettanna trained testers use during functionality and stress tests. |
| Localization Testing |
After you translate your product or web site to a non- US English language you want 2 types of localization testing and Vettanna does both. We provide testers to verify or regress the functionality and we can provide foreign language speakers to verify the correctness of the text. Many of our testers are either native speakers and/or reside in the country and use the language daily. All testers also speak, read and write English. Vettanna also provides a "bug scrub" if necessary to translate errors in written English into well written, easily reproducible bug reports for your engineers. |
Performance/
Load |
We see how the application performs in a real world environment with many users or an expected 24 hour period of users. We also look at the speed of the features and see if they are fast enough to meet users' expectations. |
| Regression Testing |
This is running a sub-set of test cases on a product. For example, if there are 650 test cases for a product. The product has just gone live after passing the tests. The engineers decide to fix something in the "registration" component. The testers will run a regression test on the registration component to verify the fix. They will not need to run all 650 test cases before they ok the fix being rolled into the live site. |
| Stress |
Does it work under stress conditions like low memory or low disk space? We also try stressful things that the user might do like create a large file, a large database or do many transactions simultaneously. |
| User Scenarios |
Many of a tester's test cases are run to just test or verify one thing, regardless of how it will actually be used. For example, most tests are easiest to verify (prove they worked right) if we use only a small amount of data. But the user will be working with as much data as they want. We also test "user scenarios" with the anticipated sequence of tasks a user will do on a normal range of data that the user will be working with. |
| White Box Testing |
All the tests above are called "Black Box Testing". This means that the tester tests the product from the UI. The tester is not concerned about what is happening in the code or on the servers. Their only concern is that the UI shows what the user expects. "User buys 1 Aerosmith CD, user gets a "Thank you for buying Areosmith" message. The black box tester isn't concerned with a web server, file server, database server, credit card processing server and all the hundreds of lines of code that executed to make it so. But, the white box tester is. The white box tester can test the "buy" code even before the pretty UI is even written. The white box tester can find that buying 60 different products will break the code. They find that out within days of the buy code being written. If left to a Black box tester, they may not find this for another several weeks. |
|
