production code

You might have run tests in multiple test runs on your production code and you want to determine how fully that code has been tested.

Using Scala just for the tests meant we got to use it in anger without impacting production code directly.

During the rest of the iteration, the team will implement the features they signed up for, pair programming on all production code.

Each target object that you test must have at least two clients: your production code, and your test case.

Note that this overhead processing is not enabled for the production code.

If your production code is safe or pure, any callable assembly method can be called and tested, in an executable file or in a DLL.

At least two vendors that I know of are shipping it in production code in their appliances.

This sample is provided for demonstration purposes and is not intended to be used without modification in production code.

Your goal is not to write your eventual production code, at least, not right away.

We have rarely used them for production code, even after four years of usage in experimental code.

Note: Production code should handle requests for attributes that do not exist in the array.

What if every line of production code were reviewed by somebody who was intimately familiar with what the code was supposed to be doing?

Yet the No. 1 concern of Google's engineers was their access, or lack of it, to Google's production code.

Expand the node for the assembly, for the namespace, and for a class in your production code.

Remember: This is an example to show the concepts and should not be implemented in production code like this.

Eventually, the code you write will either be built in the build lab or used to test production code in the build lab.

It empowered them to do so by giving them access to its production code base.

Please note the following about the code you want to test, which is referred to here as production code.

I will write up a blog entry for each LINQ operator, probably including all of the production code but only "interesting" tests.

In production code, you would not want that; but for early testing, something like what I do is helpful.

Set breakpoints in the ASP. NET unit test and in the production code for your Web site.

This generates code-coverage data for the methods in your test project, not just for the methods in your production code.

If your production code is mixed, and not an executable file, any callable method in your code can be called and tested.

Your production code project and your test project will produce distinct assemblies.

This means that you can use it in any number of different circumstances: unit tests, production code, and so on.

ASP. NET tests run in the same environment in which the production code will run.

Running tests locally lets you debug your tests and your production code.

You are a developer who authors both production code and test code.

All production code is written by two people working together.

Which one would you rather see in production code that you have to maintain?

Playing with the concepts without worrying about your production code is a lot of fun.

The development database is natural; you don't want your production code and your development environment to share the same database.

In production code, you would change this as dictated by your program requirements.

Thus, it is important to include exception handlers in all of your production code.

Did you notice that you wrote more test code than production code?

Of course, you should not leave these method calls in production code.

Before writing any production code, we'd write our unit tests.

Test cases look just like production code, and they can use the same Java beans that you use as a facade for your EJBs.

In XP, pairs of developers write all production code.

You are a developer of production code or of tests.

Our interns always work on production code.

Unfortunately, I see this one in production code more times than not.

Note that in production code you will want to include proper error handling among other things.

The best Ruby programmers I know all suggest coverage of production code of over 80%, and some strive for 100% coverage.

You cannot edit the production code.

This is a great idea when debugging, but you probably won't want to use it in production code.

With our design artifacts, we can move directly into coding a proof-of-concept, or writing the production code for our system.

As soon as the unit test code fails to compile, or fails an assertion, you must stop and write production code.

We might want to perform error checking for production code.

XPers write all production code in pairs.

I like saying that you should have at least two pounds of test code for every pound of production code.

Speaking of production code, one downside to DI is that it can feel viral.

This kind of a test project provides the ability to test the following production code

the date of pack which may be shown as a lot number or production code number;

Investigate memory problems in production code

In the ATM example, as far as the production code is concerned, the,

For example, your production code contains the following method in the BankAccount class