![]() |
![]() ![]() ![]() ![]() ![]() |
![]() ![]() |
![]() |
|
![]() ![]() |
Author | Message |
Nisha321
Newbie ![]() Joined: 02May2007 Online Status: Offline Posts: 1 |
![]() ![]() ![]() Posted: 02May2007 at 12:16am |
Hi there.
I'm going to be testing an email web application in the coming weeks, my test cases only represent functional - user end testing, Obviously there's more to testing a mail application, which I will not be covering in my testing - but I would like to point out these points in my test plan - under the section 'Aspects not being tested' I would like to highlight these as risks. Can someone tell what other considerations I should mention or at least be thinking of. Post Resume: Click here to Upload your Resume & Apply for Jobs |
|
![]() |
|
Udipti_89
Newbie ![]() Joined: 02May2007 Online Status: Offline Posts: 1 |
![]() ![]() ![]() |
What about performance aspects? You say you are just testing functional, which means you
are probably not testing the overall performance, such as checking how much mail traffic the SMTP/POP3 server can take. If that is the case, that might be something to mention that you are not doing. Strictly, it is hard to say without knowing more about the Web application. For example, does it accept control codes? Does it allow for HTML formatted messages? As you say, there are a lot of things you can test with e-mail applications but a lot of it depends on what the application is supposed to do in the first place. |
|
![]() |
|
![]() ![]() |
||
Forum Jump |
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
© Vyom Technosoft Pvt. Ltd. All Rights Reserved.