What is meant by Synchronization? How do you implement it in WinRunner?

The field of computer science has to deal with not one but two types of synchronization processes namely:

1. Synchronization of processes called process synchronization and
2. Synchronization of data called data synchronization.

Both of these two synchronization processes are quite different from each other but are related in a way. 

- In the synchronization of the processes, a certain number of processes have to come together and join in order to commit a certain action or reach an agreement. 

whereas,

- In the synchronization of the data the idea followed is of the data integration i.e., the integrity of the data is maintained by multiple copies of the data set kept in coherence with each other.

Now coming to their relation, these two distinct synchronization processes are related in the way that the former process i.e. the data synchronization can only be achieved by process synchronization primitives.

In process synchronization two particular mechanisms are applied in concurrency for ensuring that the execution of the specific portions of a software program at the same instant of time by the execution of the two concurrent processes or threads does not takes place. 

The process synchronization is quite often used in controlling the access in the following:

1. Multi- processing systems that are small scale.
2. Multi- processor computers and
3. Multi- threaded environment
4. Distributed computers that are constituted by 1000 of units.
5. Banking systems
6. Web servers
7. Data base systems and so on.

Now coming to the data synchronization, there are several examples such as the following:

1. Cluster file systems in a computing cluster

2. File synchronization

3. RAID

4. Cache coherency

5. Journaling

6. Data base replication

How is Synchronization implemented in Win Runner?

- Synchronization also exists in winrunner.

- There exists a certain synchronization point in the test script whose responsibility is to give the instructions to the winrunner regarding the suspension and continuation of the tests that are running until the software system or application that is under testing is ready for release.

- With the help of these synchronization points most of the anticipated timing problems can be solved.

- During the analog testing, the role of the synchronization point is to make sure that the window is re-positioned at a specific location by the winrunner software. 

- When a corresponding test is run, the mouse cursor is expected to move across the defined coordinates and this re-positioning of the window helps the cursor to make exact contact and that too with the proper elements of the window.

- At the point of synchronization a mismatch between the speeds of the script execution and application are witnessed.

- Three types of synchronization points have been defined:

1. Screen area bitmap
2. Object/ window bitmap
3. Object/ window property

- Another role of the synchronization point is to start and stop the application as and when required till the load of a certain user event gets completed.

- Whenever there is a difference in the speeds of the application speed and the tool speed then the synchronization process is always preferred for syncing of both the application and tool to match.

- There are certain functions called wait functions available for the same purpose as the synchronization points but it is always better to go with the synchronization points since they are capable of maintaining better uniformity among the test scripts and application. 

- For example the synchronization can be carried out for:

1. Retrieving the information from data base.
2. For making a progress bar complete 100 % and so on. 

What is meant by defect tracking automated system?

Defects and bugs upset every software system or application and thus it becomes necessary to root them out as early as possible. Tracking the defects and bugs in a software system or application proves to be quite a headache for the tester. It is like searching for one particular fish in an ocean.

Over the years new and advance technologies are being designed to improve the defect tracking methodologies and thus relieve the testers and developers of this headache. Most of the testing processes are now being automated and one of the resultant of this effort is the “defect tracking automated system” which is all what has been discussed in this article.

About Defect Tracking Automated System

- As the name of the system itself suggests it is a tool which tracks the defects and bugs all by itself with the help of the automated processes.

- This defect tracking automated system is easier to use and operate and implement.

- It can carry out many of the testing processes on its own, some instructions from the tester are required.

- The tester just has to sit back and justify the outcomes.

- The automated working of this defect tracking system is what makes this system different from the others.

- Automation is something very common nowadays in the field of computers and this feature has allowed the testers who have less knowledge and experience to carry out the testing process with confidence.

- This is so because this automated defect tracking system makes use of a few commands and simplified options to guide the tester to carry out the whole process so very efficiently and it is so very user friendly.

- There is no need for the tester to mug himself/ herself up with the knowledge of the whole process because anyways the system is smart enough to handle all the processes itself.

- This even makes it easy to teach it to the other fresh testers who don’t have any experience.

- Another feature of defect tracking automated system is that all of its functions are self explanatory.

- The idea of having an automated system has to be simple and easy to understand otherwise it is of no use.

- The evaluation of the defect tracking system in terms of its efficiency and detection rate is also very important concern and helps in deciding for the better defect tracking automated systems.

- But, for the evaluation of the tracking system one needs to know about its specific features and understand the work flow of the system.

- He/ she should be able to relate it to the requirements of the application under testing.

- Also, the defect tracking automated system needs to be in sync with the current bug tracking process.

Requirements of the System

- Before you start evaluating your defect tracking automated system, make sure that you have identified all the requirements of the system because these requirements are required to guide the evaluation process.

- These requirements need to be converted in to a features list like one shown below:
1. Adaptability
2. Change history
3. Customizable fields
4. E mail notifications
5. Security
6. Web based client
7. Work flow

- Some defect tracking automates systems can also be used to track the other types of issues like:
1. Test cases
2. Purchase orders
3. Support calls etc.

If the tracking system that you are using has been specifically designed for the purpose of bug tracking then you will have a hard time in adapting the system to track the other issues. Before starting tracking the bugs make sure that you have set the right commands to the system.

What is meant by defect leakage?

Defects can be defined as any discrepancies that can disrupt the functioning of a software system or application and often they are known to give nightmares and headaches to the software testers.

WHAT ARE DEFECTS?
- Defects are responsible for the production of incorrect or unexpected results and abnormal behavior of the software program.
- Defects are a consequence of the mistakes made by the software developers.

It is very difficult to set straight a buggy program. There are so many concepts that revolve around these defects. One of such concepts is defect leakage and we will be discussing it here in this article.

DEFECT LEAKAGE
- You can imagine water leaking out of a container having holes in it. We can take the defect leakage in the same context and define it.
- The defect leakage can be thought of as a phenomenon in which the defects leak out in the entire software system or application.
- It is due to the presence of the means for the escape of the defects.
- No present software testing methodology is so efficient that it can discover or dig out all the errors and bugs.
- Even after many times of rigorous testing still many bugs remain in the software system or application hidden and undiscovered.
- These defects are discovered later during the latter stages of the software development life cycle.
- Such defects are said constitute the defect leakage factor.
- Tracking the defect leakage is very time consuming process as well as effort consuming process.

APPROACHES FOR FINDING DEFECT LEAKAGE

APPROACH #1:
- The commonly followed approach for finding the defect leakage is the matrix method.
- The defect leakage can be tracked down using a standard matrix provided you can spare much of your time for following this approach.
- You will require to analyze all the defects and determine where actually the defect would have been discovered when those stages were in progress.
- Defect leakage indicates a lot about your programming efficiency and testing skills.
- If a lot of gap exists in your findings then it indicates that your testing and programming efficiency is quite low.
- In some cases it happens that you find defect leakage in the unit level which you could have discovered then and there itself and if not there at least that could have been caught at the level of the integration testing.
- The gap here that we are talking about is nothing but the difference between the actual defect logging time and ideal defect logging time.
- Defect leakages add to greater headaches than the usual defects so try avoiding them as far as possible by following a proper testing strategy and an effective test plan.
- All you need to do is to keep all your processes systematic and organized.
- If you are having a lack of time and need a fast completion of your testing work, then there is a greater probability that you may leave many bugs and errors here and there and later have problems with the defect leakages.

APPROACH #2:
- Another approach that you can follow is using a defect tracking automated system.
- This system files up a detection phase whenever a bug is logged.
- This bug is then rectified in the injection phase.
- Following this approach you can easily define the bug slippage also.
- You can also define the areas in which improvement is needed.
- This approach requires appropriate categorization of the defect injection phase.
- The categorization depends on the perception of the tester.
- A leaked defect is the one that could not be discovered during the usual testing but showed up during the production of the software.
- The documentation for the defect leakage is not produced by the quality assurance people.
- The reason why a defect was missed during the testing is often probed by the program managers.

What is a System? What are general principles of system?

System is an:
- integrated set of inter-operable elements;
- it consists of group of entities or components;
- interacting together to form specific inter-relationships;
- organized by means of structure;
- working together to achieve a common goal.

In defining the system boundaries,a software engineer discovers the following:
- entities or group of entities that are related and organized in some way within the system, either they provide input, do activities or receive output;
- activities or actions that must be performed by the entities or group of entities in order to achieve the purpose of the system;
- a list of inputs;
- a list of outputs.
Entities that are involved in this system are the applicant, club staff and coach.

General Principles of Systems
- The more specialized a system, the less it is able to adapt to different circumstances.
- The larger the system is, the more resources must be devoted to its everyday maintenance
- Systems are always part of larger systems, and they can always bepartitioned into smaller systems

There are two types of systems, namely, man-made systems and automated systems. Man made systems will always have areas for correctness and improvements. These areas for correctness and improvements can be addressed by automated systems. Automated systems consists of computer hardware, computer software, people, procedures, data and information and the connectivity that allows the connection of one computer systemwith another computer system.