Re: OT: Looking for som Basic/easy test questions..

They do have small real projects to work on. One is doing well, one is
not. The one that is not, I gave "homework" to - in the form of reading
and doing the problems in the first 5 chapters of a book. He had the
weekend to do it. I told him that he should have done this the first
week.  To be fair to both of the new people, as well as to have a
benchmark - I gave the test to both of them.  It is more along the lines
of something for the personel files.

-----Original Message-----
From: Discussion forum for developers using Windows Forms to build apps
and controls [mailto:[email protected]] On Behalf Of
Ron Young
Sent: Tuesday, April 24, 2007 2:49 PM
To: [email protected]
Subject: Re: [DOTNET-WINFORMS] OT: Looking for som Basic/easy test
questions..

Do you think you might be better off if you gave them a little project
to
build?

Something like a login screen would let you inspect various aspects of
their
progress.

Specify that the application will have one form, LoginForm. That form
will
have two TextBoxes for username/password, two Buttons for Login/Cancel.
You
could probably specify that the app allows the user to specify the role
they
want to login as, Admin or User (something like that). And that the user
can
make that choice via RadioButton controls. They (the developers) will
also
need to use labels appropriately.

The logic to validate username/password is hardcoded into the app.

Specify the need for validating the input. At least the length of the
input
has to meet some requirements. Validation could occur at button_Click
time,
or in the Validating event, or in the LostFocus event, where one of
those is
likely the best candidate.

Specify any naming conventions and comments in code.

Having them work as a pair to start with might be interesting.

Also, let them use SDK docs, any books they got, etc. How well they can
navigate SDK docs is an important skill. Observe how they use the SDK
docs
to say look up what the Validating event is all about, and if they can't
do
it efficiently, then that's an area they need some work on.

After they do that, they can apply some experience to answering the
questions you listed.

Ron

-----Original Message-----
From: Discussion forum for developers using Windows Forms to build apps
and
controls [mailto:[email protected]] On Behalf Of
Stacey
Levine
Sent: Tuesday, April 24, 2007 9:14 AM
To: [email protected]
Subject: [DOTNET-WINFORMS] OT: Looking for som Basic/easy test
questions..



I have two brand new developers that have been working for two months
now. Some of that has been self study.  I wanted to come up with a very
basic Winform type test to see how they are doing.  Some of the
questions are below. I would appreciate it if you had suggestions for
some other very basic questions.  Thanks.



Stacey

1.       What control would you use if you wanted to display static
information on a screen to a user?

2.       What control would you use if you wanted to display information
to a user that the user could possibly type over?

3.       On most controls, including the two in the previous  questions
- what property do you set that controls the string displayed?

4.       What event is fired when the users presses a button?

5.       What main control holds the other GUI controls that makes the
screen that is displayed to your user in a program?

6.       What is this called? (checkbox image)

7.       What is this called?  (radion button image)