E-learning testing and application testing

What is the difference between E-learning testing and application testing?

e-learning Testing
Test Partners have experience of testing a wide range of interactive e-learning applications including:

Flash-based e-learning applications for 3 - 5 year olds
CD-ROM based applications for children with special needs
Content assessment of a series of web-based learning courses for patients with a variety of medical conditions
Web-based learning courses for medical professionals including the course authoring application and course management system
CD-ROM based learning applications in a variety of European and Far Eastern languages
A highly complex server-based learning management system designed for tens of thousands of users in dozens of companies. Several of the HTML / Java based courses were also tested

Application Testing
Application testing deals with tests for the entire application. This is driven by the scenarios from the analysis team. Application limits and features are tested here.

The application must successfully execute all scenarios before it is ready for general customer availability. After all, the scenarios are a part of the requirement document and measure success. Application testing represents the bulk of the testing done by industry.

Unlike the internal and unit testing, which are programmed, these test are usually driven by scripts that run the system with a collection of parameters and collect results. In the past, these scripts may have been written by hand but in many modern systems this process can be automated.

Most current applications have graphical user interfaces (GUI). Testing a GUI to assure quality becomes a bit of a problem. Most, if not all, GUI systems have event loops. The GUI event loop contains signals for mouse, keyboard, window, and other related events. Associated with each event are the coordinates on the screen of the event. The screen coordinates can be related back to the GUI object and then the event can be serviced. Unfortunately, if some GUI object is positioned at a different location on the screen, then the coordinates change in the event loop. Logically the events at the new coordinates should be associated with the same GUI object. This logical association can be accomplished by giving unique names to all of the GUI objects and providing the unique names as additional information in the events in the event loop. The GUI application reads the next event off of the event loop, locates the GUI object, and services the event.

The events on the event loop are usually generated by human actions such as typing characters, clicking mouse buttons, and moving the cursor. A simple modification to the event loop can journal the events into a file. At a later time, this file could be used to regenerate the events, as if the human was present, and place them on the event loop. The GUI application will respond accordingly. A tester, using the GUI, now executes a scenario. A journal of the GUI event loop from the scenario is captured. At a later time the scenario can be repeated again and again in an automated fashion. The ability to repeat a test is key to automation and stress testing.

one of my friend is working in e-learn testing(learning management system)........Is it possible to change her carrer from e-learn to application testing?

[QUOTE=devic8;24462]one of my friend is working in e-learn testing(learning management system)........Is it possible to change her carrer from e-learn to application testing?[/QUOTE]

Hi,

It is not a that much tough task to change the domain from elearning to application testing as per the testing perspective. But before testing an application you need to be trained in the Domain in which you are going to test such as Insurance or Banking or Retail etc., Since the Domain knowledge is main thing when you do testing as to check whether all the business requirements are covered.

Regards,
Ganesan

yes Ganesan is right........and it hardly matters what is the kind of testing u r doing....the domain knowledge matters...
for ur friend the experience of e testing will be an added advantage.....the experience will be counted..

so,best of luck for ur friend.

can u explain about the designation "quality assurance"?wat they will do,nature of job,responsibilities etc?

[font="tahoma"][size="2"]hi devic8,

Quality Assurance is a job which would be more related to process management and improvement. We see that various companies are certified differently. Some are cmm level 3,4,5 and few are cmm-i certified.

These certifications basically deal with the way the processes are aligned in the organization and checking if companies activites are in-line with the defined processes. We have various standards as set by quality bodies like iso,cmm, six sigma etc.

A quality assurance individual job would be to work as part of an sepg group or quality team. Responsibilities would be to define standards which would in short be a combination of best practices. He would further have to ensure whether all project activities are aligned with the set processes. He would also need to define metrics, measure and lead the project / company on the path to continous improvement.

Incase a company is cmm level 2, he would need to define goals for 3 level and ensure progress to next level.

We have a seperate quality management system in almost all companies where all these laid down quality policies are listed. Defining qms is also part of a quality assurance individual.

Cheers........[/size][/font]