this is a question 
Please somebody explain how to generate INPUT TEST CASES FILE(in.txt) and how this is different from custom inputs,and own generated simple test cases using loops and adjustments.
Yes hemant_dhanuka rightly said you stole my words… this is exactly what i want to convey to admin please please make test cases public after the contest is over…since sept17 when is started coding i can think about number of good problems which i lefted just because there was no way lefted to do them even after attempting them so hard… editorials helps a lot they give us a more or less same or different approach which makes us learn new things sometimes but this question remain unanswered “what is wrong with this approach…what is…” and asking this question on forums is silly since how can anybody give time to your code as much as you have given and you understands it better than the reader… there are some points about why test cases should be reavealed like russian website codeforces
(1). when somebody have tried a particular approach and have synchronised each part of code seperately and days have been spent on that.
(2). somebody may not have good friends(coders) around him in colleges so no source of help except website.
my request to good/experienced coders please advise me
While I think keeping the judging test cases confidential is appropriate, there is a case for having some more challenging small test cases (if applicable to the problem) in editorials, or perhaps even directly in the practice version of the problem. Often the sample test cases given don’t do much more than test input and output formats.
I also like the idea of reporting test case results as happens in the %age pass problems - it’s a little frustrating to “go back” to a one-state report after problems where you get a table of outputs. Some kind of indication of the scale of the test case might make this even more useful.
Yaa really this would help alot in many ways like it would save our time, lessen the questions posted on discuss, would make us aware of different type of corner cases and more. and it would be after the contest is over, so there will be no problem I too request @admin to add this feature
For WA, yes I can understand. But how will it help for TLE? You wont be possibly inspecting the huge arrays of size {10}^{6} to analyze your solution? Is there some tool or something which helps here?
@vijju123 No bro, i don’t have any tool. In “TWOFL” problem my all test cases were passed out less than 2.3 sec but 3 cases is not passing even in 8 sec… i am doubtfull that may be in my code have any infinite loop… so if i have test cases than i can checkout wheather i am geting ans in 10 min/100 min/…(it means TLE) or i am not getting answer after waiting for long than for sure any infinity loop is running
@pshishod2645 bro, No one “wants to” post code on forums to find where code is failing but after trying to certain level(giving 200% percent) when one think now he cant do anything further, its good to ask on discuss forum to know whats wrong in previous approach rather than skipping that question or trying other approach
No its not infinite loops xD. Since each file only has a single TC, its very possible to get large variations over time. I faced that too. For me, TC 1 of task-3 was failing. Had to optimize my code 
@pshishod2645 its not compulsory to look at testCases… if one wants to try more he/she can try more without looking at test cases
Making test cases public, well, to be honest small cases can help. It was an idea for my future editorials to keep a testcase bank (couldnt do it in ltime60 due to lack of time to analyze solutions).
We cannot force codechef to reveal them, and more often than not they are maximal cases with N=1000 in smaller ones and N={10}^{5} in larger ones.
@vijju123, What if the editorial includes a link to the test files? The test files will hardly exceed 6MB in size. Once downloaded, it’ll be upto the users whether they want to wait until “Notepad” responds, or they want to keep trying to find out the corner case without it…XD
He is talking about making them public after contest so the analogy of ACM ICPC doesn’t hold valid. Besides, in codeforces you can see the testcase for which your code fails after the contest and it is very helpful in practice. The suggestion to do the same on codechef is a very valid one.
@sarthakmanna - Its essentially revealing the test cases at the end of the day. While I agree that one can put in corner cases there, I doubt that codechef will agree to reveal all the test cases. Its something the team is very particular about.
Larger ones are not revealed by CF fully. Smaller edge cases can be put up by editorialist. That can be done, but it needs analysis of what contestants are doing to figure out what can be corner cases for various approaches.
I agree editorialist can do that nicely… but with help of problem setter and tester the “public test cases” can be made of excellent quality… And they ll be more useful…
PS: Adding some corner test cases on editorial is a very good idea…
Though I also agree with @admin to not to reveal whole test case file as finding your own mistakes is kind of “fun” and a “skill”… Initially I was also frustrated and many people even get frustrated due to not revealing test cases in every contest… But after sometime I enjoyed that…
And in fact now I have hardly any question which was not submitted and got AC even after knowing logic properly… I learnt how to write neat bug free codes… And that is a skill I aquired by codechef…
And even I don’t get TLE’s due to lack of minor optimizations… If I got logic then AC is for sure… though it may take sometime… For eg. In VSN I got many wrong answers due to lack of practice in handling large double values… so eventually “not revealing” also helps…
#but as suggested by @vijju123 the idea to post some small corner cases in editorial is very good… And even it don’t reveal the whole test cases file and spoil the fun of debugging…
That is when u need help of other solutions or ur friends or discuss… If it would be easily available then everyone will give up earlier… ik it’s upto us but then too if it was easily available then why a “beginner” will go for debugging…