|
Alexei V. Karas - TeamAQA
Software Development Engineer Test (aka Technical QA Lead) Celenia Software a/s, http://www.celenia.com
Contact e-mail: AlexKaras@hotmail.com or AlexeiKaras@gmail.com
Education:
Kiev State University, Kiev, Ukraine, major in Radiophysics
I started my IT career in 1990 as a programmer for small and medium size enterprise solutions. Since that time, my activities were related to the programming within the management of complicated entities with complex hierarchical structure, in both economic and administrative areas. With every new position and employer, my responsibilities were shifted more and more from pure programming to customer support and consulting. It was my previous place of employment where I was responsible for creating a service component for the developed solution and for solution final testing and support on customer's site. I needed tools to: a) ensure that service operated quickly enough, did not leak system resources and could operate on the 24/7 basis; and b) it was nice to have a tool that could operate with the database-based VB application to automate routine testing activities.
So it was January 2001 when I met MemProof for the first time and started to participate in the Beta programs for AQtime2 and AQtest1.5.
Later on, I participated in the Betas for TestComplete, AQtime .Net and AQtime 3.x-4.x, AQdevTeam and Automated Build Studio.
Due to my work responsibilities, AQdevTeam and TestComplete are the products I am using most of all.
I am interested in helping people to have the processes that help them do their work more effectively and with more information to make well-motivated decisions. Thus, I spent quite a lot of time customizing AQdevTeam (database contains six completely new item types and some of the original item types were greatly modified) and now some of the processes in the company are organized around AQdevTeam. As an example, I can mention a simple 'suggestion-task-task reporting' process or a complex 'requirement-test case-test case execution' one. All processes are intensively using scripting to implement notifications, items reassigning and data processing. Scripts are implemented as Server and Shared Client macros that are executed by the events, triggered when the item created/changed and linked the actions in the workflow graphs. Some of the macros can be executed from the user interface by clicking the button located on the edit form.
In the company I am working for, TestComplete is used mainly for the regression testing. Nevertheless, now we have a library of test primitives that simplify creating scripts for the closed application under test and a set of data-driven test projects organized in the test Project Suite, located on the common file share. One of the interesting moments is that this suite is coded and organized in a way that allows it to be executed by any user. Besides that, any project from this suite can be executed from the same location using the same code in a local (i.e. non-networked) mode, so tester can select only test project (or even Test Suite) that he/she needs for the current task and execute it in his/her unique test environment, but using the common code and with results reported to the common shared repository.
I experimented a little bit with Object-Driven testing and did a pilot test project, but now I am waiting for the keyword-driven technique that will become available either with the plug-in from Eric, or with (I hope so) TestComplete v.4. According to the articles I have read, it looks like this technique may make creation of the test scripts easier for the test engineers who are not very experienced in programming.
Other TestComplete features that I experimented with a little are HTTP Load Testing and Network Suites. I am expecting to have a "real-world" practice with them during the upcoming projects that use data transfer over HTTP protocol. I have limited experience in the load testing and Web testing areas, so I hope to have an interesting time soon.
I created several experimental macros for personal use using Automated Build Studio (ABS), which I very much like as well. Despite the fact that these macros are experimental, they are modular and use to a great extent such a nice functionality of Automated Build Studio like submacros and named groups (feature that is almost like submacro). Besides that, I tried Automated Build Studio in integration with TestComplete/TestExecute and I am delighted with the time- and event-triggered tasks in ABS. With the functionality of event-triggered tasks it was easy to link several macros in a way, so that they have one macro that is responsible for building the core of the solution, while other macros are responsible for building modules based on this core without the necessity to rebuild the core for each macro on the one hand, and to be sure that all applications are using the latest version of the core on the other hand.
I am least experienced with AQtime but use any possibility to master myself with this tool.
When I have free time (I mean - out of computer;) ), I like to spend it either with my family (wife, daughter and a son) or with our friends.
Reading, skiing, swimming and football (soccer) are also within my interests, as well as assembling models from the model kits (well... It was long time ago when I assembled my last serious model...).
This site looks much better in a browser that supports current web standards, but it is accessible to any browser.
Download one now
Some parts of this site will not work effectively on this older browser.
Please consider
updating your browser
|