Testers vs Supporters

[r035198x]

rofl_[__]
o 0 O

Hmmm is this going slightly off topic?

The topic is Testers vs Supporters

[Ganon11]

To get back on topic...

Which would you say is easier? Testing code or supporting code?

From my knowledge I would say testing, as that involves thinking up all the possible outcomes of a program from a specific state and seeing if any unexpected results appear. Supporting would mean going through the existing code to try and discern where an error was made.

[Banfa]

Which would you say is easier? Testing code or supporting code?

That's easy, testing because you only have to deal with the computer and the program, in support you have to deal with people who are much more unpredictable.

[tolkienarda]

personaly i would rather write the code myself and have someone else find and fix the problems.

eric

[Banfa]

personaly i would rather write the code myself and have someone else find and fix the problems.

eric

It isn't a testers job to fix the code only to find the problem. The code should return to the original programmers for fixing.

[DeMan]

you make, then you test, then you support......

i sthere a difference?

[tolkienarda]

i think that these jobs are kinda all in one. the programer builds, tests, and fixes programs. somtimes we need assistance in those various stage but it is still the programers job to do all of the steps because they can better test a program because they know all of its capabilites.
i was just saying i would like somone to fix all of my code for me rather than doing it myself (would be kinda nice)

eric

[Banfa]

No for a professional large development you need independent testing to ensure impartiality.

Testing by the programmer is not as good because the programmer has preconceived notions because they wrote the code and know how it works and may well not test the software in the way the user intends to use it.

The tester should follow a test plan agreed with the user to ensure that the program works in the way that the user requires not the way the programmer has coded.

In my company we have 2 levels of testing (one following the other)

FAT - factory acceptance testing testing performed by the programming team to a customer agreed specification

SAT - Site acceptance testing performed by the customer after initial delivery but before final sign off on the project.

[tolkienarda]

what languages do you guys write in. i've gotten a good enough grip on php, which is what i need for work, that i am ready to delve into a new language. what would you advice. I learned VB and C++ in highschool but c++ was all CLI. so what should i learn if i want to be a 'real' developer one day.

eric

[Banfa]

what languages do you guys write in. i've gotten a good enough grip on php, which is what i need for work, that i am ready to delve into a new language. what would you advice. I learned VB and C++ in highschool but c++ was all CLI. so what should i learn if i want to be a 'real' developer one day.

I would go with C, C++ and Java and you should find they all have some syntax similarities to each other and php. If you want to become Mr Microsoft then you will need to get a nhandle on .NET too.

[tolkienarda]

thanks are there any particular header files in c/c++ i should look into or just expand my knowldge of the syntax.

eric

[Frinavale]

what languages do you guys write in. i've gotten a good enough grip on php, which is what i need for work, that i am ready to delve into a new language. what would you advice. I learned VB and C++ in highschool but c++ was all CLI. so what should i learn if i want to be a 'real' developer one day.

eric

I'm really starting to like .NET.
Unless of course you're working cross platform....I'd suggest C++ or maybe Java?

[Ganon11]

what languages do you guys write in. i've gotten a good enough grip on php, which is what i need for work, that i am ready to delve into a new language. what would you advice. I learned VB and C++ in highschool but c++ was all CLI. so what should i learn if i want to be a 'real' developer one day.

eric

I'd venture a guess and say that the language does not really matter - what you have to learn is concepts such as OOP. When I started learning C++ this year, I had done nothing of it before - yet within a few weeks, I was as good in C++ as I had been in Java after studying for a year. I had learned the thought process behind problem solving in small-to-large scale projects, and these concepts were portable. The only thing to learn when changing languages is specific syntax differences, such as using NULL in C++ and null is Java.

[tolkienarda]

thanks i have been reading a book on cgi theory but would like to get out of web apps someday and move into larger projects, is OOP somthing that i should study and if so do you have any good suggestions on where to get a book or online reasource

thanks

eric

[ronverdonk]

thanks i have been reading a book on cgi theory but would like to get out of web apps someday and move into larger projects, is OOP somthing that i should study and if so do you have any good suggestions on where to get a book or online reasource

thanks

eric

Have a try on one of the following and see if that is what you are looking for.

Interactive tutorial on OOP
OO Programming Tutorial
OOP Tutorial
Don't fear the OOP (Java)

Ronald