Wednesday, August 20, 2008

How to Grant Permission to Remote Access in MySQL

If you are using Client Server architecture with MySQL database,you cant directly access MySQL database which is in the server.

To Access MySQL Database thought the network,you have to grant the permission to each do that you have to follow following steps.

Ex :- Create a database "WSO2"

1. Open MySQL Command Prompt

2. Type Following Command to grant usage permission to access MySQL

Syntax -

mysql> GRANT USAGE ON *.* TO username@[Client_IP] IDENTIFIED BY 'password';

Ex :-

mysql> GRANT USAGE ON *.* TO Chamara@ IDENTIFIED BY 'chamara123';

3. Then Type following command to Grant database Permission

Syntax -

GRANT ALL PRIVILEGES ON database_name.* TO username@[Client_IP];

Ex :-


Now you can access WSO2 Database from anywhere.

Tuesday, August 19, 2008

User Interface Testing at Glance


In Software Quality Assurance, UI Testing is most important Testing area.Because users are directly communicate with the User Interfaces.During the UI Testing Tester must concentrate to following key areas.

  • Colors of the controls and application
  • Look And Feel of the application
  • Ease of use
  • Controls up to Standard

Colors of the controls and application

        Tester should concentrate on color used to buttons,labels and other controls.if application use dark colors or very bright colors,it tired users eye.because I think middle class colors are very user friendly.

Look And Feel of the application

       Look and feel of the application is another important part.because user see the application at glance, it should be able to attract the user.other wise user will leave the application within a short Tester should see the application user point of view and test look and feel.

Ease of use

       Every task of the application should very user friendly.if user want to do some task using application,application should provide that very easy manner.for that application can use wizards,Help tips,meaningful labels and icons etc.In testing "Ease of use" of an application tester need to check wether that application follows wizards,meaningful labels,buttons,icons etc by covering all the functionalities.

Controls up to Standard

        Using application controls based on the standards is another tip for improve user friendliness in testing this section tester should concentrate whether that application follows  standard buttons,labels,text boxes,drop down boxes,control sizes etc.otherwise user may confuse with the controls application used.

Monday, August 18, 2008

What makes a good Test Engineer

A good test engineer has a 'test to break' attitude, an ability to take the point of view of the customer, a strong desire for quality, and an attention to detail. Tact and diplomacy are useful in maintaining a cooperative relationship with developers, and an ability to communicate with both technical (developers) and non-technical (customers, management) people is useful.
Previous software development experience can be helpful as it provides a deeper understanding of the software development process, gives the tester an appreciation for the developers' point of view, and reduce the learning curve in automated test tool programming. Judgment skills are needed to assess high-risk areas of an application on which to focus testing efforts when time is limited.

What makes a good Software QA engineer?
The same qualities a good tester has are useful for a QA engineer. Additionally, they must be able to understand the entire software development process and how it can fit into the business approach and goals of the organization. Communication skills and the ability to understand various sides of issues are important. In organizations in the early stages of implementing QA processes, patience and diplomacy are especially needed. An ability to find problems as well as to see 'what's missing' is important for inspections and reviews.

What makes a good QA or Test manager?

A good QA, test, or QA/Test(combined) manager should:
  • be familiar with the software development process
  • be able to maintain enthusiasm of their team and promote a positive atmosphere, despite what is a somewhat 'negative' process (e.g., looking for or preventing problems)
  • be able to promote teamwork to increase productivity
  • be able to promote cooperation between software, test, and QA engineers
  • have the diplomatic skills needed to promote improvements in QA processes
  • have the ability to withstand pressures and say 'no' to other managers when quality is insufficient or QA processes are not being adhered to
  • have people judgement skills for hiring and keeping skilled personnel
  • be able to communicate with technical and non-technical people, engineers, managers, and customers.
  • be able to run meetings and keep them focused.
What's the role of documentation in QA?

Critical. (Note that documentation can be electronic, not necessarily paper.) QA practices should be documented such that they are repeatable. Specifications, designs, business rules, inspection reports, configurations, code changes, test plans, test cases, bug reports, user manuals, etc. should all be documented. There should ideally be a system for easily finding and obtaining documents and determining what documentation will have a particular piece of information. Change management for documentation should be used if possible.

What's the big deal about 'requirements'?

One of the most reliable methods of insuring problems, or failure, in a complex software project is to have poorly documented requirements specifications. Requirements are the details describing an application's externally-perceived functionality and properties. Requirements should be clear, complete, reasonably detailed, cohesive, attainable, and testable. A non-testable requirement would be, for example, 'user-friendly' (too subjective). A testable requirement would be something like 'the user must enter their previously-assigned password to access the application'. Determining and organizing requirements details in a useful and efficient way can be a difficult effort; different methods are available depending on the particular project. Many books are available that describe various approaches to this task. Care should be taken to involve ALL of a project's significant 'customers' in the requirements process. 'Customers' could be in-house personnel or out, and could include end-users, customer acceptance testers, customer contract officers, customer management, future software maintenance engineers, salespeople, etc. Anyone who could later derail the project if their expectations aren't met should be included if possible. Organizations vary considerably in their handling of requirements specifications. Ideally, the requirements are spelled out in a document with statements such as 'The product shall.....'. 'Design' specifications should not be confused with 'requirements'; design specifications should be traceable back to the requirements.
In some organizations requirements may end up in high level project plans, functional specification documents, in design documents, or in other documents at various levels of detail. No matter what they are called, some type of documentation with detailed requirements will be needed by testers in order to properly plan and execute tests. Without such documentation.

Friday, August 15, 2008

What is Software Testing Life Cycle (STLC)

Software Testing is most important task in software development.Once you developing a software Application,you have to understand the software development life wise Software Testing Life Cycle is also parallel goes with the Software Development life Cycle.

Now I am going to explain section by section of Software Testing Life Cycle.


1. Requirement Analysis

In Requirement analysis phase need to understand of all the software requirements.for this you can use Software Requirement Specification (SRS) Document.

2. Test Case Writing

In this phase you have to write test cases by covering all the features and functionality in application.

Test Case Document should contain following sections.

  • Test Case Name :- Name Of the Test Case (Ex : Click Ok Button)
  • Test Case :- How that test should do (Ex: Go to X window and Left Click Ok Button)
  • Expected Result : - Result Of the Test (Ex : Y window Display)
  • Status : - Actual Result of test case Pass/Fail
  • Comments : - Special Remarks of the test case.

3. Test Case Executing

Executing test cases in test case Document and filling.

4. Issue Reporting

During the application testing you have to track all the issues currently having.for this you can use issue tracking tool.

5.Issue Verification

After fix the issue you reported by the developer you have to retest that.above 3,4,5 STLC phases you have to follow as a cycle until application come up to some standard.

6. Release Product

In this phase you are ready to release the have to make release notes for it.In release not contain all the areas you tested and what are the knows issues in this release application.