Best Practice for Debugging and Testing Asp.net Website

Question

User-305496339 posted

Hi Friends,

I was wondering what is best practice for debugging and testing an Asp.Net Website. For example do I just open the website in visual studio or do I need to create a solution file? Also do I create a copy and debug and test on my local machine or on the server where the website files reside ? Thanks !!!

Answer 1

User541108374 posted

Hi,

testing your application locally surely helps to find bugs faster as a developer (and are way cheaper to fix than once they're in production, according to studies between 30 and 60 times cheaper).

do I need to create a solution file

Depends on your web application. If it's .NET based then very likely already a solution file will exist. 

I was wondering what is best practice for debugging and testing an Asp.Net Website

If you're a test engineer then likely you want to have the application running on some server and you interact with it and see if the data is correctly stored in the data storage of use (usually a database) and that the business logic is rightly executed/implemented by comparing the results.

As a developer you can make unit tests and integration tests. For the visual parts you can make use of tools like Selenium to automate things. Also do performance testing and load testing on your application and improve if needed.

Kris.

Answer 2

User-305496339 posted

I greatly appreciate your reply but with all due respect that was really not the answer that I was looking for. I am working as a developer with a 10 year old website built with asp.net and I just wanted to know what is best practice regarding test and debugging environments, and I am mainly emphasizing should I test it locally on the server? We are not using unit tests, its not that complex of a website

Answer 3

User475983607 posted

I greatly appreciate your reply but with all due respect that was really not the answer that I was looking for. I am working as a developer with a 10 year old website built with asp.net and I just wanted to know what is best practice regarding test and debugging environments. We are not using unit tests, its not that complex of a website

I'll add to XIII response given your clarifications, a common approach is source control and debugging on localhost. 

Environments are remote web servers/DB servers that are not localhost.  A Development environment is commonly an anything goes environment.  Server configuration, application setup, deployments are all administered by developers.  There's usually a lot of deployments throughout the day as code gets checked into source control. 

A Test environment is more like production where configuration does not change and deployments are far less than Development.  User testing happen in the Text environment therefore a Test environment usually has specific features under tested.  Updates to the Test Environment are tied to bugs fixes that were found during user testing.   

Sometimes there is a Staging environment which is exactly like production used to verify the application will not blow up when it reaches the Production environment. 

Anyway, this is a software development life cycle question.  How you implement an SDLC is up to your but there's tons and tons of information on the Internet.  Usually the SDLC is tied to the source control you picked.

Answer 4

User1120430333 posted

Hi Friends,

I was wondering what is best practice for debugging and testing an Asp.Net Website. For example do I just open the website in visual studio or do I need to create a solution file? Also do I create a copy and debug and test on my local machine or on the server where the website files reside ? Thanks !!!

The link shows how to bedbugs using localIIS and VS for project or Website

https://docs.microsoft.com/en-us/visualstudio/debugger/how-to-enable-debugging-for-aspnet-applications?view=vs-2017