Application Center Test & Password Recovery
2 things to cover here since I encountered these 2 issues today at the same time.
1. Application Center Test
As those who have used the Application Center Test would probably know how useful it is to use this little simple tool to perform stress testing on web application - either it be a web page for sign in, web service, or web page for document upload.
PROBLEM IS: If one is trying to perform stress testing on a web page that does file upload, one will find that the test result would produce a lot of error, and the end product would be a lot of error feedback from the web page.
The reason is because when a test is recorded, there will be a possibility that a whole chunk of bytes went missing. It happens when I'm trying to upload a file with 24Kb, and only 5Kb being recorded inside the test script, thus therefore there will always be problem.
The possible cause for this could be traced back to the reason that the file is uploaded as text, and because certain files' format have a lot of unreadable character inside it, thus when ACT was trying to record it, it found out that the characters were not readable, thus discarding all of it, and making the file corrupted.
The only way to overcome this problem is to transfer the file either encoded or zip it up. Sadly though, I don't really know how to do it in either the normal HTML, ASP or JSP or the ASP.NET... But the question is, does it worths to do it just for the sake to have the web page ready for ACT to perform stress testing?
2. Password Recovery
When one has forgotten his/her password of an online account, there's always ways to retrieve it from that online site. There are some that would return the actual password; there are some that would not return the actual password but instead a very hard to remember random generated password, of which would require the user to login with that temporary password and reset the password again.
The second one is more secure probably, but it doesn't really matter in this world where nothing is unbreakable in this Cyber world. So it really depends on the developer themselves to do it, and I would reckon that the first one is much more easier to do as compare to the second one, since every way is hackable nowadays.
1. Application Center Test
As those who have used the Application Center Test would probably know how useful it is to use this little simple tool to perform stress testing on web application - either it be a web page for sign in, web service, or web page for document upload.
PROBLEM IS: If one is trying to perform stress testing on a web page that does file upload, one will find that the test result would produce a lot of error, and the end product would be a lot of error feedback from the web page.
The reason is because when a test is recorded, there will be a possibility that a whole chunk of bytes went missing. It happens when I'm trying to upload a file with 24Kb, and only 5Kb being recorded inside the test script, thus therefore there will always be problem.
The possible cause for this could be traced back to the reason that the file is uploaded as text, and because certain files' format have a lot of unreadable character inside it, thus when ACT was trying to record it, it found out that the characters were not readable, thus discarding all of it, and making the file corrupted.
The only way to overcome this problem is to transfer the file either encoded or zip it up. Sadly though, I don't really know how to do it in either the normal HTML, ASP or JSP or the ASP.NET... But the question is, does it worths to do it just for the sake to have the web page ready for ACT to perform stress testing?
2. Password Recovery
When one has forgotten his/her password of an online account, there's always ways to retrieve it from that online site. There are some that would return the actual password; there are some that would not return the actual password but instead a very hard to remember random generated password, of which would require the user to login with that temporary password and reset the password again.
The second one is more secure probably, but it doesn't really matter in this world where nothing is unbreakable in this Cyber world. So it really depends on the developer themselves to do it, and I would reckon that the first one is much more easier to do as compare to the second one, since every way is hackable nowadays.
Comments