Technology Questions

You must code EXEC CICS ASSIGN with the OPENID option.

 Test scenarios are derived from requirement documents. We follow each and every functionality (called business rules) mentioned in the requirement document. One functionality can have multiple business rules. For example, let us say in there is one requirement called “Login”. This “Login” may have various scenarios. For example, one scenario is, enter the right User ID and wrong password. The system should display an error message. Another scenario would be to enter wrong User ID and right Password. The system should display an error message. The third scenario could be to enter the right User Name and right Password. The system should allow the user to get into the system. This is how the test cases are derived from the requirement documents or from the Use Cases.

$_SERVER and $_ENV arrays contain different information. The information depends on the server and operating system being used. Most of the information can be seen of an array for a particular server and operating system. The syntax is as follows:

foreach($_SERVER as $key =>$value)

{ echo “Key=$key, Value=$value\n”; }

First thing testers are not responsible for fixing the bug they are only responsible for debugging the bug and prioritizing those bugs. These bugs are now reported in bug report template with the severity and priority of the bug. Tester assigns severity level to the defects depending upon their impact on other parts of application. Every bug has its severity and priority values assign by tester. If a defect does not allow you to go ahead and test the product, it is critical one so it has to be fixed as soon as possible. We have 5 levels as:

Critical

High

Medium

Low

Cosmetic

Htmlentities() converts all applicable characters to HTML entities. While htmlspecialcharacter()converts special characters to HTML entities. This means htmlentities( ) will check for non English language characters, such as French accents, the German umlaut, etc.

The mapreduce framework contains most of the key architecture principles of cloud computing such as:

- Scale: The framework is able to expand itself in direct proportion to the number of machines available.

- Reliable: The framework is able to compensate for a lost node and restart the task on a different node.

- Affordable: A user can start small and over time can add more hardware.

If any one want to restrict Trans-ID to single user, enter trans-id with ENQ. It won't allow any one else to use the same trans-id.

- Scheduling and executing the batch jobs.

- Configuring, starting and stopping the real-time services

- Adapters configuration and managing them.

- Repository usage, Job Server configuration.

- Access Server configuration.

- Batch job publishing.

- Real-time services publishing through web services.