So what are inputs?

You need to have some understanding of what inputs are more common than others, what inputs better represent typical inputs than others.

It takes the 2 inputs.

Running something on all possible inputs is impossible, unless it's a problem where the inputs are constrained, so there's only a few possible inputs.

And obviously their inputs go into other people's their outputs go into other people's inputs.

And it's driven by these inputs.

Now we have our 3 inputs.

And that we have 3 inputs

So we can validate their inputs.

Give it some example inputs and outputs.

So the lookup procedure takes 2 inputs.

I'll call this the price of inputs.

There could be any number of inputs, but it has to match the number of inputs the procedure expects.

Namely, given some inputs, what are the outputs?

The inputs were 9, which corresponds to Iroquois.

Second, not only should your approach take a minimum of tests for these 5 inputs but also for other arbitrary inputs.

If your program gets the same answer on all inputs as loops forever, then your program loops forever on all inputs.

The part I'm going to make unobservable is where, exactly, I receive plus 100 and where I receive minus 100.

Since there are 3 inputs, we need 3 names.

I can write inputs from bed. I don't know.

In the lucky search problem, we have 3 inputs.

Wow can we get these kinds of video inputs?

I'll add the element to each of these inputs.

We can have as many inputs as we want.

So we have some inputs here and these are on the, in the left, in the first column, we have just the inputs.

With find you would pass in one or two inputs.

You're just like your mother and her stupid GDR inputs.

So, problem is defined by the set of possible inputs.

We're going to take in 2 inputs a and b.

We can have the same code operate on different inputs.

Maybe we test it out on a bunch of inputs.

For this one, it does terminate for all inputs n.

And by construct, it's something unobservable as opposed to real physical observable objects that you might encounter in engineering problems for example.

In this example, we again might have our unobservable cancer C, but now we're running 2 tests, test 1 and test 2.

A procedure is something that takes inputs in there can be more than one does some work on those inputs and produces outputs as results.

These inputs are sometimes called operands. They are sometimes called arguments.

But then, these are inputs into a whole set of things.

That means it's hard to find a colliding pair of inputs

Problems that take inputs just like what we've been looking at.

And again, it comes up with a number of interesting inputs.

All of these interesting inputs cause the program to run properly.

And now we want to do the biggest for 3 inputs.

Whatever we pass in as inputs to the procedure will be what that code operates on and it can do different things depending on those inputs and it produces outputs that tell us the result, based on the inputs that we passed in.

We click on ask Pex, and now you see a number of interesting inputs, and these would all be inputs which cover various parts of the code.

We can think of our humans as also mapping inputs to outputs.