Testing your databases via C# tests -
I have been tasked to test our database. This is a test database and we can do anything we want and easily roll it back. I have been given this work because we are still in the design phase (which means that any change can be made at any point during the project ... change the person's name [first_name] for first name column and later I changed my name to [first name]. My goal is that when we make changes, then we need to set some estimates for the kind of pain that we do, so that we can plan ahead of time We can expect these types of changes even during production. / P>
There are items I have on my list and there are written tests for it:
- < Use the word "null" (not a literal null but rather "null") because dynamic SQL can flip thinking that you are actually empty. We have detected this because a person with the last name "null" Up for Use of single quotes because the possibility of dynamic SQL is not a single quote. Then, someone has created the cause of the crash in the name of someone.
Never before did this, I know all this that the accident can occur. Other ideas out there? Users can log in while trying to emulate e data. Edit 1: Our problem is that we have a search screen with about 25 fields that they can search. Some of these search fields are simple (e.g., first name) Somewhat less simple (With a date less than 2 but less than 2, with category 2, or 2 in any given period, category 4). The search screen allows the user to choose different operators and predicts with each of these 25 areas. Is there a better way to handle dynamic SQL? I am at a situation and at a point in time where we can change something different if it is better.
Edit 2: I do not know that it is worth mentioning, but we use LINQ to store the processes. My research has shown that dynamic LINQ will not need to do this like a dynamic SQL query to do this. Though may be wrong.
what ''; Drop-table person; - "Can there be an accident?
To avoid SQL Injection Techniques, you should consider removing your strategy from dynamic SQL with parametric queries.
For testing, you can use transaction questions and NUNIT to test a fashion unit. Speaking strictly, unit testing should separate your application from the data store so that d Test parts can be tested without access penalties for access and modification of Ta Parties. However, you can use very similar techniques to test your data store, if you decide, Lane in TestFixtureSetup Make the bin and roll it back to the testfisectardown, the way your database will return to the original state when your test is completed.
Time should be aware of as the test is a performance penalty to store data in this way, however, to unit test your balance will not perform as well as application - assuming the application of the rest of his performance is tuned.
Comments
Post a Comment