QA Testing

MSG Systems Romania msg systems România – filiala concernului german msg systems AG, una dintre primele companii din domeniul IT din Germania – este prezent de aproape 3 ani pe piaţa locală de IT Software. Astăzi, msg systems România se poate mândri cu cea mai extinsă echipă de specialişti în domeniul dezvoltării software SAP din Transilvania – o echipă care se află în creştere permanentă.

La ora actuală, echipa din Cluj, împreună cu colegii de echipă din Germania, lucrează la unul dintre proiectele cele mai mari din istoria concernului (dimensiune prevăzută: >4000 ani-muncă). Pentru clientul VIG, lider de piaţă în asigurări în Europa Centrală şi de Est, se dezvoltă un software pe platformă de SAP pentru gestionarea tuturor proceselor de asigurare. Spectrul de servicii asigurate acoperă întreg ciclul de viaţă al unui sistem modern de gestiune a afacerii: de la activităţi de consultanţă la implementare, customer support şi Lifecycle Management ale produselor software standard ca soluţiile SAP.

Colaborarea între msg systems şi SAP în proiectul amintit nu este singura de acest gen. Concernul german este partener strategic al SAP pe tot domeniul Insurance: soluţii software pentru asigurare şi reasigurare. Cea mai mare companie de IT software din Europa, SAP, creează şi dezvoltă produsul ERP (Enterprise Resource Planning) nr. 1 la nivel mondial. Pentru branşa asigurări/reasigurări, se bazează pe competenţele strategice unice ale msg systems pentru dezvoltarea soluţiilor software din domeniu.

Dimensiunile deosebite ale proiectelor derulate inclusiv la Cluj-Napoca necesită extinderea continuă a echipei SAP, asigurată cu precădere prin creştere organică, adică lărgirea echipei prin formarea profesională, încă din timpul facultăţii, a studenţilor interesaţi să devină specialişti software în domeniul SAP. Aceste programe de instruire se desfăşoară prin două parteneriate strategice, derulate deja de doi ani, cu Universitatea Babeş-Bolyai, Facultatea de Ştiinţe Economice şi Gestiunea Afacerilor, respectiv cu Universitatea Tehnică din Cluj-Napoca, Facultatea de Calculatoare. Descriem aici o poveste de succes, anual, câte 10-15 noi colegi alegând să-şi înceapă cariera în cadrul msg systems România. În plus, susţinerea acordată studenţilor şi absolvenţilor – pentru a înlesni trecerea din mediul academic în industria IT – este o direcţie în care s-a investit foarte mult. În fiecare an compania oferă posibilitatea de practică, susţinere pentru realizarea lucrării de diplomă şi doctorat, precum şi stagii de instruire sau internship. În paralel cu activitatea profesională, fiecare angajat are posibilitatea de a învăţa limba germană prin intermediul cursurilor organizate zilnic în cadrul companiei.

Centrul de competenţă din Cluj menţine un standard ridicat: prin şansa de a lucra în echipe mixte cu alţi profesionişti din lume în cadrul msg systems, pe proiecte inovative şi complexe, angajaţii msg systems România devin, în timp, specialişti recunoscuţi şi apreciaţi de clienţii de primă mână ai companiei. De asemenea, msg systems România operează cu precădere în domenii de vârf, ţintind optimizarea proceselor de business ale clienţilor prin implementarea unor soluţii complete software de ultimă generaţie. De exemplu, un atare domeniu, necesitând o fuziune de cunoştinţe informatice cu unele economico-manageriale, este Business Intelligence (BI): o tehnologie ce permite companiilor să utilizeze tehnici de analiză a datelor operaţionale pentru a obţine indicatori sintetici de performanţă, ce servesc managementului la evaluarea evoluţiei istorice a afacerii şi la determinarea de previziuni economico-financiare.

În cadrul msg systems România funcţionează în prezent şi unul dintre cele mai mari centre de development SAP Business Intelligence din Transilvania. Specialiştii clujeni s-au format în cadrul realizării, în comun cu colegii din msg Germania, a proiectelor pentru modulul SAP FS-RI – (Financial Services – Reinsurance (reasigurări) – development si QA Testing, pentru clienţi ca Munich Reinsurance (cifra de afaceri 45,5 Miliarde Euro), VIG şi Audi.

Despre msg systems:

Cifra de afaceri: peste 400 mil. EUR
Fondată în ianuarie 1980
Concern multinaţional cu filiale în: Austria, Elveţia, Olanda, Singapore, SUA
Situată în Top 10 al firmelor de IT din Germania; Global peste 3.000 de angajaţi, din care peste 90 de specialişti în Cluj-Napoca
Furnizor de servicii de consultanţă şi soluţii IT pentru diferite branşe: industria automotive, asigurări/reasigurări, domeniul financiar-bancar, domeniul energetic
Clienţi: Audi, BMW, Daimler, VW, ADAC, Allianz, Vienna Insurance Group, ING, Munich Re, E-On.

Sursa:  ziuadecj.ro

Differences in functional testingThe task of testing the accurateness of functions is explained by additional influencing factors such as diverse browsers and browsers settings. The heterogeneous hardware configurations as well as the different possibilities of Internet access and consequently application use must already be taken into account when testing the individual user functions. These additional factors place increased demands on the methodical approach and qualifications of testers. In addition, individual tests should be repeated in diverse environments in order to discover differing behaviour, for example in different browsers. Further relevant factors are the cache behaviour of the browsers, security settings and the activation of functionality such as Java Script or the support of ActiveX components. This is an important area in practice because many environment properties which actually should not influence the application do indeed have an effect. Examples are the inadequate representation of objects using a certain screen resolution, failure of the application when using a certain browser and problems executing Java scripts on certain operating systems, just to name a few.

A decision matrix can help when analyzing the factors to tested. The parameters in the matrix are the values to be converted in testing (browsers X, Y and Z; operating systems A, B and C; and further influencing factors) and the estimated risk for combination of values. In essence, the risk for any combination of values can be calculated as the product of the probability that a failure will occur and the costs associated with that failure. The result is a matrix with weighted pairs of values which can be used as a basis for decisions on test case specification and the repeated execution of tests.
Functional test cases, for example, are repeatedly executed on different platforms of the Internet application with different browsers. This places increased demands on test automation.

Flexible test tools lend a helping hand here. Many capture-playback tools now allow a test to be recorded using one browser (e.g. Internet Explorer) and replayed in other browsers (e.g. various versions of Netscape Navigator).

Google Optimizer!? Are there any issues present? Google has an Website Optimizer tool for website testing and optimization. This tool allows you to increase the value of the websites and of course the traffic. As it stands, the experiment URL we conduct the experiment on splits traffic between the original page, the a page and the b page. This is great when directing people to the page they want to be in the experiment.
However, if they have a link on a website that points to the URL where the experiment URL is, there is no way for users to go only to the control page. So for example, someone clicks on a link, and sees page B. But what if the original page has crucial information and navigational content? Users will just be frustrated and leave.
Is there any way to specify whether we forward them or not? Or is it
all or nothing, basically?
To solve this, one must create a mirror page of the original page they are testing. The problem is that adjusting PPC campaigns to this new URL lowers their quality score. If they point a PPC Campaign to a test page, will the Quality Score be for the original page, Page A or Page B?
My guess is the original…

With other words, there might be an issue present…
Let’s say we’ve got two landing pages being tested: index.html and index2.html
Index.html is obviously our regular home page and serves as the control. index2.html is a copy of that homepage with some changes. The most significant change is that the number of links and access to the entire site is limited when you’re on index2.html. So, in essence, index2.html is the homepage of a little mini-site that keeps new visitors quarantined unless they take the desired conversion action.

The problem arises when they take the conversion action and are redirected to the main site. The whole site works for them as long as they don’t click the home button. But as soon as they click the home button the GWO script intervenes and sends them back to the index2.html instead of permitting them to go to the real home index.html.
Is there any way to stop this from happening? It’s basically interfering with our preferred traffic flow and is no doubt frustrating our visitors.

Hmm not easy, but how about create an index3 page which is a clone of your normal homepage but doesn’t have the GWO tags on it. Then after the use converts, you redirect him to index3 page.

So…running an AB test but for certain people, always having them go to A (and essentially not partipcate in the experiment), you can add some custom webserver code that only add the GWO tags if the visitors meet certain conditions (e.g. if they come from such and such a referrer, don’t add the tags).

Read more here: Software QA

Visit one of the best Software Company!
Evoluxis is an outsourcing company specialized in software development and eager to satisfy a wide range of clients from Europe, Asia or America. The main target of Evoluxis is to become a top software company in Romania and one of the best outsourcing solutions in Eastern Europe. Click here for more Info:

Evoluxis your Software Development Expert

Development of cars, you can check here a list of your favorite cars: Cars

Classical Test Levels

In software quality assurance the principle of “divide and conquer” has asserted itself just as in software development. In a software development there is the differentiation between the development of individual classes or modules, the integration of the classes and modules into an application with neightbouring applications, for example via interfaces or common data.

Each of the different development and integration phases necessitates appropriate quality objectives or a different perspective. As an appropriate response to the different objectives in a process as a whole, the entire QA process is divided into different test levels. The different QA objectives, responsabilities, methods, and tools are asigned to these test levels. The figure shows one possible partitioning of the test objectives into test levels as practised in many enterprises today.

Documentation testing

In the first level, the documentation test, the accurateness of specifications and design decisions are examined. The focus is on functional and technical design documentation, for example the results of an object-oriented analysis or design. The design documentation is subjected to a test in the form of a review with the participation of developers and domain experts.

In the developer test the developer or a tester from the development team tests the correct implementation (coding) of the specifications. During functional testing the acurateness of the implemented functions are tested from a user’s point of view.

Functional testing

Functional testing can be further divided into functional system testing, which focuses on the individual functions of an application, and functional integration testing (application testing or integration testing in the small), which tests the correct integration of the individual functions within an application. Sometimes an overall integration test (integration test in the large) is also carried out in which the correct integration of the application with other complete systems is verified.

Non-functional testing

Non-functional testing takes place in parallel to these levels, concentrating on non-functional quality characteristics such as performance, fault tolerance, reliability, usability and instability.

You can read more here: QA for Internet Applications

Many Internet applications are targeted towards a very heterogeneous group of users. The intention of a bookseller with his shop application is to be open and accessible to every user able and willing to spend money. This also means that only few general statements can be made with any certainity about the user’s expectations, his education, his computer knowledge and many other factors relevant for the design of screens and business processes. The result of this is the quality requirement that the look and feel of the Internet application be as intuitive and generally understandable as possible. In contrast to cassical application development, it cannot be assumed for Internet applications that idiosyncratic or otherwise unusual features in the functionality or the interface can be compensated by user training, manuals or help texts. The importance of this quality requirement therefore becomes corespondingly greater.

Read more:  QA Internet Applications

Usability