|
I am working in C++ (using VC++ compiler) so what is the best tool which gives thread wise analysis (profiling)
|
|
|
|
|
|
|
I am looking for beta testers for an app I have written in C#. The application is called 'Multiconvertor', and converts from metric to imperial & others for a range of stuff like length and temperature. The app was written as a learning exercise in C# (.net 2). I am a total n00b to programming, so there's bound to be mistakes somewhere! Email me at hc060jd@orange.net if you are interested, as I haven't been able to find anywhere to host the files so that they can be downloaded by anyone. You can have the uncompiled source in C#, or the exe installer. This program will only work with .NET 2 and above (so not 1.1).
Cheers, JD
Sometimes I think we're alone in the universe, and sometimes I think we're not. In either case the prospect is quite staggering.
-Arthur C. Clarke
|
|
|
|
|
Hmmm. When you have written it as a learning exercise, why do you want to have it tested? And how intensively?
|
|
|
|
|
Hi,
I didn't find ant Tab in the code project for testing people. As we have to do the scripting for the tools like WinRunner, QTP LoadRunner etc we need a special tab for Testing. Can anyone help me in this to inform it to the site maintenance authority.
|
|
|
|
|
plz anybody can explain the types of bugs, and their effect in the application.
thanks
swapna
|
|
|
|
|
You'll find many answers if you research exception handling for various OOP languages. One language should be enough for diverse material, except perhaps that type safe languages may somewhat de-emphasize type mismatch errors. Research error codes and the built-in exception types (yes, exceptions are actually types in OOP) of mainstream languages such as C++ and C#.
|
|
|
|
|
plz provide me the information about the bug types
thanks.
○♠•
|
|
|
|
|
Sorry, answer is too broad for a forum post.
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
|
|
|
|
|
I have came accorss these question, could anybody help me out to get.
thanks.
♠
|
|
|
|
|
Have you googled what Dr. Watson does?
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
|
|
|
|
|
|
i m not getting clearcut difference among these three...if anyone can provide differences with example it would be very nice to understand this....
Harish Singh
BE CSE
|
|
|
|
|
Basically, you can think of performance testing as a way to test how an application (or group of applications) will perform under normal running conditions.
Load testing is a way to test how an application (or group of applications) perform under various loads. For example, if you were load testing a multiuser, network application, then you'll want to test it multiple times with different numbers of users simulating several different patterns of network traffic.
Think of stress testing as running tests to overload the application (or group of applications) in order to observe what happens. The goal here is to try to break the running application hoping to discover things like potential buffer-overflow bugs, various resource contention issues (like deadlocks), dangling pointers, data validation bugs, etc. In a way, stress testing can also be thought of as load and performance testing on steroids.
Again, my descriptions are brief, and hopefully my analogies are enough to help you get started. Nevertheless, you'll probably want to spend some time researching various testing methodologies, because this is a very rich topic.
|
|
|
|
|
there is a difference between the tests like performance checks the time taken to execute the application, load checks how many users can access at the moment.
swapna
|
|
|
|
|
|
|
|
Following definitions are according to ISTQB syllabus (International Software Testing Qualification Board, something like a standardisation gremium)
"Load testing" tests the behaviour of a system (or component or whatever) with increased load, e.g. the number of users on the system, number of transactions etc... Goal is to determine what load can be handled by the system.
"Stress testing" evaluates a system at or beyond the limit of its specified requirements. Since that is exactly what you need to do for load testing (to see how much your system can handle), both, load and stress testing can be regarded equivalent.
"Performance testing" determines the performance of a system, i.e. the degree to which the system accomplishes its tasks within given constraints in terms of time and throughput rate.
Example: You have designed your system for 10 users. In load / stress testing, you test its behaviour with 1 user, 2 users, ... 10 users, 11 users. Focus of your test here is not the speed (it may get terribly slow with 10 users) of the system but if it does not break, if it really allows 10 users (and not only 8) etc.
In performance test, you verify that your system meets given timing constraints. For example, if your requirement is that the system should respond within 10 seconds in any case, you will focus on stopping the time. Of course, you will have to test the speed with a different number of users (1,2 ... 10) logged in, since that may affect the system. So somehow, both test strategies are intertwined.
Did this help a little bit???
|
|
|
|
|
A client of mine seems to think I charge way to much for web design and flash movies. Is there anyone willing to look over some of the things I have done for him and let me know what you would charge? If you can help, please email me Caldwell598@aol.com
Thanks
|
|
|
|
|
How much do you charge? If you don't mind me asking
|
|
|
|
|
$50/hour for any web related work (html, flash, etc.)
|
|
|
|
|
Caldwell598 wrote: $50/hour for any web related work (html, flash, etc.)
That sounds modestly high but still in the reasonable range. Depends on work quality. Do you have any sites for people to see your sample work?
|
|
|
|
|
Hourly charges allow for abuse. Jobs should be by contract unless there is something about the job which is so hypothetical its cost cannot reasonably be projected (accurately enough to be bound by contract). A person who maintains a real estate website at $50 per hour is very expensive if they produce 1 or 2 pages an hour. A person who produces higher quality pages at a rate of 20 or 30 pages per hour however (by pre-designed format of course) can make 2-300$ per hour at $10 per page. In the 90's purported web boom (false), the Industry Standard (a principal e-magazine about the false boom) published figures showing per-page costs to be in the $1,000 range in the early 90s, to $1,300 per page or so in the later 90s. If I could have found those clients, I'd have made many millions. In truth, much web development competes with relatively amateur technical skills. If you make good earnings, it almost certainly will have to be by contract and high skill. There should be few clients these days willing to hire anyone by the hour.
|
|
|
|