Testing new Java programmers who want to work in Oxagile we use different methods: interviewing, multiple-choice questions etc. We think that “classical” approaches to recruiting should be combined with new breakthrough technologies.

Let’s take certification of Java programmers as an example. It is well known that many tests for certification contain a large number of issues with different variants of answers (so called multiple-choice questions). Such tests are not very effective, because probationers can easily find many answers concerning API reading documentation or source code. In this way we can’t test their ability to program, which largely consists of the ability to think logical and to formulate algorithms in a proper way.

So betterprogramming.com, the company from San Francisco, decided to fix this problem. Its specialists published test that offers to solve several problems instead of answering the list of questions. Java programmers expected to implement some simple algorithms. Source code, written by a developer can be executed on the server, and then user can get his/her results (they depend on submitted code and time).

There are a lot of words said about web development and functional programming methodologies. Usually they are oriented to development mostly and do not deal very much with testing. So should testing have a separate methodology?

It is not a secret that quality software is one of the most important requirements for a customer. It often doesn’t matter the timeframe or even the budget of the project, but whether the end users will be pleased with the product developed. So the importance of testing is great and on some projects good testing is even more valuable than good development. Anyway this doesn’t mean that testing should have a separate methodology. As testing is a very agile and flexible process, which closely connected with web application development, there should be the same methodology for testing as for development.

Testing is flexible enough to choose the best process to achieve the result easily and quickly. It can be various, depending on the development methodology, project team specification and customer’s goals.
If you think of a separate testing methodology – just take all the best practices together and work out your own testing methodology!

Nowadays software testing is a rapidly growing up sphere. And software testing engineers may be found employed in different sectors. Lots of methodologies are widely known:
-Agile testing;
-Extreme testing;
-Scrum testing;
-White Box testing;
-Traditional Black Box testing and others.

The Black Box testing is the most popular and called for in many companies around the world. For years experts had been developing different costly commercial tools to lessen testing efforts and to increase the efficiency and quality of software testing, but lots of them were nonviable in practice. Later in 2001, some testing experts offered to create the software utilities for their manual-and tool-automated testing efforts.

And today at every seminar or training there are courses and lectures teaching testers more technical topics, including programming, networking, and databases. In the past and certainly today quick, efficient and profitable testing is in great demand. One of the ways to reach these goals is using .NET application software for testing projects. Although .NET languages are powerful enough to accomplish some useful testing tasks, testers and developers must have enough knowledge to write the code.

But first of all let’s discuss the automated software testing in general. At the beginning let’s look at some of the important management issues involved when starting automated testing, like guidelines for when and when not to automate testing, what kind of personnel requirements are needed to address and how to build an automated testing team. In later articles we will discuss the advantages and disadvantages of using two .NET languages, Visual Basic (VB) .NET and C#, for test projects and utilities.

Unfortunately there isn’t enough information out there yet to help test experts to use programming for testing purposes. Most of the publications are geared for software developers, not testers. Using .NET languages for testing requires a shift in the future. A tester may go to different courses, trainings (for example, standard Visual Basic course) to wonder how it could ever be used on a test project. These trainings and a lot of articles, books explain just how to use the controls and the ways to create a great application with user friendly interface. But the tester doesn’t care about that so much— actually he wants to know how to get to the system information and other testing-related data using code or how quickly develop a utility. But the reality is the following – a tester must know how to use .NET languages as soon as possible on a test project:
– How to get access to the DB easily and quickly;
– How to get access to the Windows Registry to return distinctive application data;
– How to create a front end with basic controls to view test information and results as soon as possible
– How to get access to the appropriate .NET Framework library functions that return relevant information about the platform, files, registry, operating system, and so on.

These questions are just the beginning, but they reflect some of the things the testers have used to accomplish their testing tasks.

Why are.Net languages a good choice for testing? Actually .NET languages are not testing tools. They are a set of languages used for developing software. And it’s required to answer why it is better to use C#, Visual basic to reach testing goals instead of C, Java, Perl and PHP.

Scripting languages (for example Python, Perl, Rexx, VBScript and others) have a large group of supporters. Why not use those? As an actual fact none of those scripting languages were invented with testing in mind. These languages can be a good advantage for testing software, particularly if they are already installed and a tester has quite good experience. But if there are testing engineers with skills in .NET languages, so they will be a great choice. Also if the application is being written in any of .NET programming languages, in that case it may be a reason for the testing engineers to use it for automation software testing. But it’s not absolutely required to use .Net languages for automation of .NET applications. It’s a delusion.
But for Windows platform it’s a perfect choice that will give the power to do whatever you need. The Framework libraries have a lot of things to provide the successful automation testing. For example, .NET programming can be used for a lot of hidden applications’ operations testing. Scripts can be developed to get access to the system environmental variables and performance counters. Automated scripts can check the correct loading and retrieval of the data from files. It’s obvious that the .NET programming languages are powerful development tools makes them showing promise of future success and able tools for software testing. So it’s very important for test engineers to study .NET languages and to begin use them in everyday working practice.