Header Ads

15 Important concepts of Quality

Quality:

Quality software is software that is reasonably bug-free, delivered on time and within budget, meets requirements and expectations and is maintainable. However, quality is a subjective term. Quality depends on who the customer is and their overall influence in the scheme of things. Customers of a software development project include end-users, customer acceptance test engineers, testers, customer contract officers, customer management, the development organization's management, test engineers, testers, salespeople, software engineers, stockholders and accountants. Each type of customer will have his or her own slant on quality. The accounting department might define quality in terms of profits, while an end-user might define quality as user friendly and bug free.


Test build Manager:

Test Build Managers deliver current software versions to the test environment, install the application's software and apply software patches, to both the application and the operating system, set-up, maintain and back up test environment hardware. Depending on the project, one person may wear more than one hat. For instance, a Test Engineer may also wear the hat of a Test Build Manager.


Database Admin:
Database Administrators, Test Build Managers, and System Administrators deliver current software versions to the test environment, install the application's software and apply software patches, to both the application and the operating system, set-up, maintain and back up test environment hardware. Depending on the project, one person may wear more than one hat. For instance, a Test Engineer may also wear the hat of a Database Administrator.

Component Test:
A Component Test is basically a load test to check if the different components are working fine. A system is builds up with database,servers,network, storage devices etc.
To test those component individually and connected is called component test.
This is to test the architecture of a system .

What is a Build?

After completion of development dev team release to testing team.After sanity testing if any changes required dev. team modifies the build and releases with different build name.

Sanity Testing:
Sanity testing is a basic,initial and very quick test of flows to make sure that the system can operate and process at least a minimal workload. It can be treated as an entry criteria into further testing. This is to make sure the application is stable,testable, and to avoid wasting time trying to test an application which fails frequently.

Test Build Managers, System Administrators, Database Administrators deliver current software versions to the test environment, install the application's software and apply software patches, to both the application and the operating system, set-up, maintain and back up test environment hardware. Depending on the project, one person may wear more than one hat. For instance, a Test Engineer may also wear the hat of a System Administrator.

Test/QA Team Lead:
The Test/QA Team Lead coordinates the testing activity, communicates testing status to management and manages the test team.

Technical Analyst:
Technical Analysts perform test assessments and validate system/functional test requirements. Depending on the project, one person may wear more than one hat. For instance, Test Engineers may also wear the hat of a Technical Analyst.

Configuration Manager:
Test Configuration Managers maintain test environments, scripts, software and test data. Depending on the project, one person may wear more than one hat. For instance, Test Engineers may also wear the hat of a Test Configuration Manager.

Test Schedule:
The test schedule is a schedule that identifies all tasks required for a successful testing effort, a schedule of all test activities and resource requirements.

Good Code:
A good code is code that works, is free of bugs and is readable and maintainable. Organizations usually have coding standards all developers should adhere to, but every programmer and software engineer has different ideas about what is best and what are too many or too few rules. We need to keep in mind that excessive use of rules can stifle both productivity and creativity. Peer reviews and code analysis tools can be used to check for problems and enforce standards.

General Testing Process:
The general testing process is the creation of a test strategy (which sometimes includes the creation of test cases), creation of a test plan/design (which usually includes test cases and test procedures) and the execution of tests.

Test Engineer/Tester:
A Test Engineer is an engineer who specializes in testing. Test engineers create test cases, procedures, scripts and generate data. They execute test procedures and scripts, analyze standards of measurements, evaluate results of system/integration/regression testing. They also...

  •  Speed up the work of your development staff;
  •  Reduce your risk of legal liability;
  •  Give you the evidence that your software is correct and operates properly;
  •  Improve problem tracking and reporting;
  •  Maximize the value of your software;
  •  Maximize the value of the devices that use it;
  •  Assure the successful launch of your product by discovering bugs and design flaws, before users get discouraged, before shareholders loose their cool and before employees get bogged down;
  •  Help the work of your development staff, so the development team can devote its time to build up your product;
  •  Promote continual improvement;
  •  Provide documentation required by FDA, FAA, other regulatory agencies and your customers;
  •  Save money by discovering defects 'early' in the design process, before failures occur in production, or in the field;

Save the reputation of your company by discovering bugs and design flaws; before bugs and design flaws damage the reputation of your company.

A Testcase:
A test case is a document that describes an input, action, or event and its expected result, in order to determine if a feature of an application is working correctly. A test case should contain particulars such as a...

  • Test case identifier;
  • Test case name;
  • Objective;
  • Test conditions/setup;
  • Input data requirements/steps, and
  • Expected results.

Please note, the process of developing test cases can help find problems in the requirements or design of an application, since it requires you to completely think through the operation of the application. For this reason, it is useful to prepare test cases early in the development cycle, if possible.
Powered by Blogger.