What is developer checkout?

Question

1.00/5 (4 votes)

See more:

This is my first project. I got to know some new words. What is developer checkout? What is program specification documents? How to write unit test cases?

Posted 29-Jan-16 12:43pm

Member 12229842

Updated 11-Jan-18 8:51am

Add a Solution

Comments

Sergey Alexandrovich Kryukov 29-Jan-16 19:06pm

Without any context? It's no good. Most likely, you mean the term from Revision Control Systems and practice. Different system have somewhat different concepts of "check in", "check out", "populate", "commit", and so on, especially the distributed ones, as opposed to the centralized...

Same thing is with the questions formulated in the body of the question. They lack context. Besides, I'm not sure they are not off-topic, some of them. And then, the whole idea of asking such questions on the forum is not really productive. You need to learn some basics first and later ask more focused questions. Imagine you are listening to the lecture on development process and at the end ask the author these questions. The lecturer may express some surprise: "What do you think I was talking about whole hour?". But if you ask a random person, even a competent one, at random time, that person may ask you: "who are all those people?", as in one well-known joke.

Writing unit tests depend on the testing techniques used or the unit testing framework, if you use one. Again, it's about the context.

—SA

Member 12229842 29-Jan-16 21:57pm

They said we have to do developer checkout when the code is ready for deployment

Sergey Alexandrovich Kryukov 29-Jan-16 22:13pm

Are you sure you recognized all the words correctly? :-)
—SA

Member 12229842 29-Jan-16 22:37pm

I know all three are not related. I will elaborate a lil.. The project just started.. I did not get any work yet. I know what PSD and Unit test cases are,but never really saw. So, Just wanted to ask here if anyone could tell me or give an example.Just trying to learn more...

And about developer checkout just know that it should be done while you hand over the code to QA team.

So I just wanted to know lil more about everything i posted. Sorry that I posted those question in very immature way.

It wont happen again.

Wanted to do more that just coding for assigned module.

Anyways thanks :)

Sergey Alexandrovich Kryukov 30-Jan-16 0:06am

No, it's all right. Eventually, in some fields most of us will do something immature. That's why we comment on answers, to improve your chances to get help.
In this case, you need to do some homework with your team, ask them the question on general direction of development, tools to be used, accepted practices. You need to start with something certain. Than you have to read on the topic to get some basic idea. Then your questions will be on something which you have an idea on, but, say, seem to be confused...
—SA

Dave Kreskowiak 29-Jan-16 20:12pm

What do you mean by "this is my first project"? The first application you've ever written? Are you completely new to writing code or what?

Member 12229842 29-Jan-16 21:53pm

Yeah it's my very first project.. And I am hearing all these things from my seniors and I don't have a idea

Sergey Alexandrovich Kryukov 29-Jan-16 22:13pm

Ask them what did they mean. Why asking it at this forum?
—SA

Member 12229842 29-Jan-16 22:38pm

Yeah sure. Will try that.. Thanks :)

Dave Kreskowiak 30-Jan-16 0:01am

Asking them wasn't your first response? Wow. You've got a LOT to learn. Asking questions is a skill and one you better learn fast. Hiding your shortcomings from those around you is a sure way to get yourself in trouble.

Sergey Alexandrovich Kryukov 30-Jan-16 0:06am

5!—SA

Member 12229842 30-Jan-16 0:12am

:)

Member 12229842 30-Jan-16 0:20am

Actually i ask them lot of questions, thats how i come to know lots of things... but some times they speak from their level means as senior developer or architects.. so i get confused...

And i guess i should learn the question asking skills, as i tend to ask a lotttt(i guess 100 questions a day) to my colleagues ;)

Sergey Alexandrovich Kryukov 30-Jan-16 0:33am

Look, this is wrong attitude. "They speak from their level..."

I would suggest you assume they talk to you on this level because they respect you (maybe giving you an advance credit). When we speak, we usually don't have complete information on our partner's background and will gladly accept reasonable feedback. You should not just listen. It's your responsibility to establish better communication by saying "Wait a minute... I understand only this, but I have no idea what is that", "Will you elaborate on this..?" Believe me, people expect and welcome that, because they also try to find a common ground for a conversation and don't want to waste their time on fruitless talking.

You have to become a partner, this is what they expect from you...

—SA

Member 12229842 30-Jan-16 0:38am

I guess i got the answer of my question... thanks :)

Sergey Alexandrovich Kryukov 30-Jan-16 0:59am

You are welcome.
—SA

ZurdoDev 30-Jan-16 11:20am

Post as solution please.

Sergey Alexandrovich Kryukov 30-Jan-16 20:49pm

Excuse me, what would you suggest to post?
—SA

ZurdoDev 30-Jan-16 20:52pm

Not sure. But OP said you answered them.

Sergey Alexandrovich Kryukov 30-Jan-16 21:16pm

I'm also not sure. I think what is said it said; the publication does not have to be a formal answer.
Thank you.
—SA

Member 12229842 31-Jan-16 18:29pm

Ohh sorrybfor delay.. as you said i should ask my seniors whenever i dont understand anything in conversation...so that was my answers

I am planning to ask my seniors whatever questiins i have

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Michael Haephrati · Answer 1 · 2018-01-11T08:51:00

Checking out source code
The term "Check out" is taken from the metaphor of a public library where one can "check out" a book. A checked out code, is locked from others to check out the same code, whilst creating conflicts. When you are done with your edits and enhancements, you return the code back (check in).
Please read [this article] to understand further.

Functional Specifications Document
A functional Specifications Document (or "Specs"), is a document where the product / project manager describes the functions that the program, you are working on, should perform.
See also: this article.

Unit Testing
Unit Tests are small parts of a whole (program), usually a single function or a short pice of code, which can be tested separately and automatically. See: this article .