Hi I am testing some .NET code, as well as functional testing the business workflows I would to look out for any specific .NET issues there may be. Does anyone have any pointers for me?
I have discovered a particulary 'good' issue by entering the greater than symbol (I can't post the character either it seems) followed by a alphabetic characters in any of the input fields it throws a disturbing error.
I have 'SQL injection' mentioned to me can any one throw some more light on this for me (As non-technical as possible) as to best way to utilise it or any other key Gotcha's
I can't think of any .NET specific issues to look out for.
In terms of your issue with the greater than sign, it is probably an encoding issue with the browser interpreting it as the end of a HTML tag. One of my recent projects had lots of problems with such characters (e.g. the NOT symbol, double/single quotes, ampersand, pipe). The problems became worse when the product was internationalised.
SQL injection is a complex topic. Here's a collection of links to get you started
Thanks for that Bill, I'll investigate those links. NOt sure if this is the correct Etiquette for forums but as an addition to my original request.
Can anyone give me some pointers to Performance testing for .NET? Do I need to make any special considerations. Any common Issues working with .Net? I have very limited resources both personnel and financial.
Performance analysis and testing is another quite complex subject. Again I can't think of any .NET specific issues.
There is a Performance Testing forum that you can post specific questions to and also pick up quite a bit of information.
Originally posted by StuartUK: Hi I am testing some .NET code, as well as functional testing the business workflows I would to look out for any specific .NET issues there may be. Does anyone have any pointers for me?
<font size="2" face="Verdana, Arial, Helvetica">If you end up writing a custom test harness (in VB.NET or anyother .NET language) and use if for performance testing you could have problems with garbage disposal (objects are not immediatly released with results in excessive memory usage, usually noticable during performance tests).
Also if your test harness interfaces with COM objects you can get similar problems because the COM objects are not immediatly released by the .NET framework.
However, you will only have these problems if you write your own test harnesses, and there are solutions for when these problems are encountered.