Viktor Tokar has over 4 years of experience in software testing with a focus on manual testing. He has experience testing a variety of applications including trading, risk management, oil company management, payment processing, and PDF tools. He is proficient in test planning and execution, defect reporting, collaboration, and guiding less experienced testers.
Decoupled System Interface Testing at FedExTechWell
If you work in a large-scale environment, you know how difficult it is to have all the systems “code complete” and ready for testing at the same time. In order to fully test end-to-end scenarios, you must be able to validate results in numerous systems. But what if all those systems are not available for you to begin testing? Chris Reites describes “decoupled testing,” an enterprise-level solution for managing interface data for capture, injection, simulation, and comparison all along your testing paths. Decoupled testing provides the ability to validate and independently test systems without having to rely on end-to-end testing. This is accomplished by capturing intermediate interface transactions at pre-determined, critical points during processing and comparing them against previously captured or generated expected results. Chris shares a case study on how this approach has benefited FedEx on critical customer-facing systems.
Decoupled System Interface Testing at FedExTechWell
If you work in a large-scale environment, you know how difficult it is to have all the systems “code complete” and ready for testing at the same time. In order to fully test end-to-end scenarios, you must be able to validate results in numerous systems. But what if all those systems are not available for you to begin testing? Chris Reites describes “decoupled testing,” an enterprise-level solution for managing interface data for capture, injection, simulation, and comparison all along your testing paths. Decoupled testing provides the ability to validate and independently test systems without having to rely on end-to-end testing. This is accomplished by capturing intermediate interface transactions at pre-determined, critical points during processing and comparing them against previously captured or generated expected results. Chris shares a case study on how this approach has benefited FedEx on critical customer-facing systems.
k fault tolerance Mobile Adhoc Network under Cost Constraintsugandhasinghhooda
A network topology is a K-FT topology if it can endure K number of link failures, however to find a reliable hardware topology for a set of nodes keeping the total cost of the links within a predefined budget, is a challenging task, especially when the topology is subjective to constraints that the topological network can tolerate K link failures keeping total cost of network within budget. This problem has been addressed in this paper where in a novel algorithm is proposed that uses N X N matrix to represent the cost between the participating nodes, and uses K-FT topology to tackle the fault tolerant problem of Mobile Adhoc Networks. Intention is to achieve optimal resource utilization and fairness among competing end to end flows. A network topology is said to be K-FT if and only if every pair of node is reachable from all other nodes for K link failures. The algorithm has been tested for wide range of node sets and the result obtained there of suggest that the proposed algorithm finds better solutions in comparison to Genetic Algorithm.
Twenty odd years trending and still we have few (if any) examples of truly integrated wearable technology examples that have reached market scalability. Most examples of wearable technology are akin to a “cottage-industry”– handmade, bespoke and expressive, more couture than ready-to-wear, reminiscent of the pre-industrial revolution methods of production for textiles and clothing.
The challenges we had 20 years ago remain largely the same despite growing market interest in the area. But with new developments in rapid prototyping and e-textiles we are in a much better place today to address some of the major roadblocks in taking wearable technologies to scale and disrupting the current manufacturing infrastructure.
1. Viktor Tokar
QA Test Engineer
Cell phone: +48533238505, E -mail: TockarVictor88@gmail.com, Skype: VitR_88
Summary
Four years of experience in Software Testing. Having a proven ability to create and carry out test cases. Also
have great communication skills with foreign and native QA Leads and Management. Self-motivator and a
team player who possess self-discipline of getting the job done without minimum supervisions.
Technical Skills
Technologies: VMware, TestLink, WCFStorm, JMeter, ActiveDirectory, Citrix, WTS (Windows
Terminal Server),Visual Source Safe, Document Management Systems(LiveLinkSharePoint,
NetDocuments, DeskSite, FileSite, WorlDox), Cloud Connectors (Evernote, Dropbox, Nuance Cloud
Connector etc. ), Digital Signatures and Certificates, Team Foundation Server.
Operating Systems: Windows XP SP3 (x32, x64), Windows Vista SP2(x32, x64), Windows 7 (x32,
x64), Windows 8(x32, x64), Microsoft Server 2008 SP2, Arch Linux, Linux Ubuntu (Basic knowledge).
RDBMS: MySQL(Basic skills), Oracle DB (Basic skills)
Other Software: Acronis, Ghost, Paragon
Summary of Work Experience
Name of Employer | | SMT Software (Contractor for Credit-Suisse)
Date of Employment | | October 2015 — Present
Role | | QA Test Engineer
Testing Approach | | Manual
Projects: Macro Trading Applications (Including trade of Bonds, Swaps, Futures etc.), Risks Aggregation
Application
General description: Macro Trading application is used by banks all over the world for Global trading of
Bonds, Swaps, Futures etc.
Risks Aggregation Application is the system that takes data from different sources and aggregate it to
show risks for traders
Responsibilities and Key Accomplishments:
2. - Creating and performing test plans and test cases that are based on documentation that was provided
by analysts;
- Collaborated with big team of programmers and analysts;
- Participated on meetings with customers to provide an information about QA activities that will be
provided during the integration of different features to the system;
- Found issues and reported with the best description and additional info;
- Provided regression testing after a new features has been added;
- Discussed main problems and defined followed tasks with team;
- Supervised and guided newcomers;
- Fixed technical remarks in documentation and Technical Requirements;
Name of Employer | | WincorNixdorf GmbH
Date of Employment | | May 2014 – September 2015
Role | | QA Test Engineer
Testing Approach | | Manual
Projects: Nixdorf Applications for Mineral Oil Systems (NAMOS), NAMOS Central (Head office
application) , NAMOS retail (Back office application) , NAMOS Compact (Point of sales application).
General description: NAMOS applications are used for automatic business processes for oil companies at
different levels, from top management of the company (NAMOS central) to cashier at his Point of Sales on
Fuel Station.
NAMOS products are used by top oil companies like GPN, BP, SHELL and others. Application
includes lot of different functions, like automatic delivering forms that sending to suppliers of gas stations
for different items (shop items, fuel items) to financial reports for some period of time (Day, Month, Year).
NAMOS central is a strong management product that used in the central office of the company that
includes all possible tools for correct and fast responses for changing market conditions.
NAMOS retail is a back office application that used at the fuel station and can manage all processes
for successful work of the station. NAMOS retail can provide information to central office like financial
reports, sales amounts of different items for different periods and for each cashier at the point of sales.
NAMOS compact is a point of sales application that has intuitive interface and used for sales of shop
items and fuel items on the station. Also it has a strong tools for integration with different hardware.
Responsibilities and Key Accomplishments:
- Creating and performing test plans and test cases that are based on documentation that was provided
by analysts;
- Collaborated with big team of programmers and analysts;
- Participated on meetings with customers to provide an information about QA activities that will be
provided during the integration of different features to the system;
- Creating and testing XML files for correct integration with 3’rd parties applications;
- Found issues and reported with the best description and additional info;
3. - Testing of Data exchange between NAMOS applications (HOS,BOS,POS);
- Provided regression testing after a new features has been added;
- Discussed main problems and defined followed tasks with team;
- Supervised and guided newcomers;
- Performed localization tasks on different languages;
- Fixed technical remarks in documentation and Technical Requirements;
- Made business trips to Germany test laboratory for electronic payments test and NAMOS compact
testing;
- Testing Point of Sales and Outdoor Payment Terminals;
- Also testing Electronic Payment Systems with different payment cards;
- Setup full HOS-BOS-POS systems on a different hardware for tests in test laboratory;
- Had a great experience in communication with foreign colleagues for solving some
urgent problems and maintaining testing process as it is;
Name of Employer | | IBox
Date of Employment | | August 2013 – May 2014
Role | | QA Test Engineer
Testing Approach | | Manual
Projects: Payment services and terminal client
General description: The main principals of these application is to make payment through terminal easy
and accessible to every client.
Product has intuitive interface that make it very easy to use.
Responsibilities and Key Accomplishments:
- Creating and performing test plans and test cases;
- Collaborated with big team of programmers and analysts in agile environment;
- Verification of the correct XML response from server
- Found issues and reported with the best description and additional info;
- Provided Payment server testing using JMeter, Mongo DB and Oracle DB ;
- Manual testing of Terminal client UI using Mongo DB and Oracle DB for usertracking and
monitoring ;
- Provided regression testing after a new features has been added;
- Discussed main problems and defined followed tasks with team;
- Supervised and guided newcomers;
- Performed localization tasks on different languages;
- Fixed technical remarks in documentation and Technical Requirements
4. Name of Employer | | TranSoftGroup
Date of Employment | | June 2012 - August 2013
Role | | QA Test Engineer
Testing Approach | | Manual
Projects: PDF related applications
General description: Powerful programs that are created to deliver industry standard recognition of PDF
files. Convert, create, modify and secure - the main principals of these applications.
Great performance and compatibility with MS Office applications and multiple network and
cloud
connectors are standards for throughout many versions. Applications support a lot of international visual and
text format standards, such as: PDF, jpeg, bmp, tiff, docx, xls, rtf, etc.
Also specialises in making recognition of text and visual info through its powerful OCR engine
and
supports voice recognition. Process of recognition in “a second” the main idea of programs. Also available
Batch Processing with support of scheduled tasks which are very useful for enterprises and companies.
Responsibilities and Key Accomplishments:
- Collaborated with a 15+ member team;
- Found issues and reported with the best description and additional info;
- Provided testing using ADSMS, WTS services for Network for support and compatibility;
- Tested Security and Protection of PDF files;
- Provided regression testing after a new features has been added;
- Analysis of OCR correctness;
- Discussed main problems and defined followed tasks with team;
- Had a great experience in communication with foreign QA Leads for solving some urgent
problems and maintaining testing process as it is;
- Performed localization tasks on more than twenty different languages;
Certificats:
- ISTQB Foundation Level
Language Skill Written Spoken
Ukrainian Native Native
Russian Native Native
English Upper Intermediate Upper Intermediate
Polish Intermediate Intermediate
5. Academic Record
Date of Studying | | September 2005 – July 2010
Name of Institution | | Kiev Slavonic University (KSU)
Specialty | | Management. Economist
Personal Data
Date of Birth | | 19 October 1988 (19/10/1988)
Nationality | | Ukrainian
Marital Status | | Single
Hobbies | | Music, Books
Additional Data
Foreign Passport | | Yes
Driving License | | Yes
Else | | on request