DOCSLIB.ORG

Functional Testing -Test Automation -Compatibility Testing

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Functional Testing -Test Automation -Compatibility Testing -Functional Testing -Test Automation -Performance Testing -Security Testing -Compatibility Testing -Test team outsourcing Functional testing Functional testing is the basic and the most critical part of the software testing. Implement the testing from the uses perspective can find the defects and bug, which developers unable to detect during the code review process. No matter how the code quality is, the defects that found in the functional testing are not acceptable. UniTesting China Company from the autonomous point of view, and not biased on client’s development team, to helps clients implement the product functional testing to measure software product quality, and to help them improve software product quality. These kinds of testing are from professional testers’ perspectives; it cannot be replaced by client's own development team and business team. UniTesting China Company has a complete test methodology and the appropriate tools to ensure software functionality testing. Function tests include: 1. Solution and Plan Before the functional testing project starts, or in the first step, is to make sure the testing solution and plan. In test plan, the project team has to make clear who is going to do the test, when the testing work start, and the resources that the project team needs. Project manager has to keep a principle in mind: time and resource are limited, so you have to carefully control the range of testing work. That is why, in test solution, the project team must answer the question: what is to be tested, how to test. For example, to determine: - The emphasis to be focused on - The difficulties we might to have - The key techniques we are going to use - Which part is the one that errors are easily exposed? - Which part is more concerned about by the customer? 2. Understanding the Functional Requirements Understand the functional requirements from the user's perspective. This process normally requires obtaining specification from the customer and then having a further study and discussion, which in order to ensure our test team is able to understand software requirements. A very important step is to determine the functional requirements test coverage. UniTesting China company divide coverage into three types, which to better ensure coverage: Test Execution Defect Type Comments Test Case Guided Case Covered Significant for Customer Test Criterion Case Uncovered Conventional Easily to Guided Detect 3. Functional Test Design After totally understanding the requirements, we will perform the testing in the form of writing testing cases. The design content is not only including function descriptions from client, but also involves some required test criteria which based on our testing experiences. For the test implementation, it also needs to design and create the effective test data. 4. Test Execution Execute functional testing, and run all the test cases and entry defects/issues/bug into bug tracking tool. Regularly monitor bug resolve situation. UniTesting China Company takes the advantage of test automation solution to help client save cost and time at the appropriate time and at the appropriate area. Regarding on testing automation, please refer to…… 5. Report UniTesting China Company is not only focusing on functional testing of software, but more importantly, we make the analysis of software quality and present a comprehensive evaluation based on the testing results. Meanwhile, we will offer our suggestion from the technical point of view to help our customers to improve their software products. Test Automation UniTesting China Company believes that the proper application of the automated testing will bring lots of values to customers: for example low cost, speed-to-market and high quality. The wide range of application of automated testing is a trend. In our testing solutions, the automated testing is a very important component. With the functional testing and stress testing process; automated testing technology will be recommended implemented. Automated testing has the following benefits: 1- Bring More convenient to the regression testing process, especially when more frequent changes happen, the effect is obviously. Due to the regression testing and the use case action is completely designed, and the test results are entirely can be expected, make the regression testing operate automatically, which can improve test efficiency and reduce regression testing time. With the Agile development model is getting popular, under the iteration development mode; the trend of automated testing application in the regression testing is inevitable. 2- More complicated testing can be operated. One of the obvious benefits of automated testing is to use less time to run more testing. 3- Test the reusability of the cases. The automated testing is commonly used scripting technology, thus, it may need to do the very small amount of changes or even not have to do the changes, which achieve to implement the same use cases in different tests courses. 4- To increase software confident. Since the testing is performed automatically, so there is no negligence and error in the implementation process, the process entirely depends on the testing design quality. Once the software is tested through a strong test, the trust of the software will be naturally increased. However, UniTesting China also believe automated testing is not universal in the current environment, therefore, before automated testing application, assessment and analysis should be carried out. At the meantime, based on the automated testing experiences and knowledge, the automated testing solutions and consulting service that UniTesting China company offers are as below: - According to the customers' current testing process, testing planning and software architecture analysis, we will confirm whether it suit for automated testing as well as which part is suitable for automated testing. - Automated testing solution design, which including automated testing tools selection, automated testing process determination and the automated testing training. In our company, we have a mature methodology which can simplify automation process. This methodology contains components reusable and key word driven script, which can maximum process flexibility as well as re-use resources that could reduce and automation period and marketing cycle launch time. Moreover, it also can guarantee the clients obtain the best value from their investment. UniTesting China Company implements the following testing automation tools: 1- HP. It including HP WIN Runner, HP Quality Center, HP QTP, HP Performance Center, HP Test Director, HP Web Inspect. 2- IBM. It including IBM Rational Robot, IBM Rational Site Check, IBM Rational Functional Tester, IBM App Scan Suite. 3- Borland. In including Silk Test, Silk Performance, Optimizeit Suite. 4- Compuware. It including QA Load, QA Center, File Aid, Devpartner, Test Partner. Performance Testing The purpose of performance testing is to: 1. Assess if the system meets the performance standard 2. Find bottleneck and identify the root cause of the problem 3. Measure the capacity and other performance attributes like concurrent users, response time. 4. Look for architectural changes, performance tuning to be done to meet the performance criteria The performance testing of UniTesting China Company is a comprehensive performance testing solution, which including: Stress testing, performance testing, load testing, Capacity test, soak testing, scalability testing, and reliability testing. - Load test is to measure response times of the system to see if the application can support expected maximum number of concurrent users. - Stress test is to measure server response times at varying loads starting from low load, medium load through high load to verify application's stability and validity. - Capacity test is to determine the maximum number of concurrent users an application can manage without compromising response time. - Soak testing is to test a system at high load for prolonged periods of time. A soak test would normally execute several times more transactions in an entire day (or night) than would be expected in a busy day, to identify any performance problems that appear after a large number of transactions have been executed. - Scalability testing is an extension of performance testing - it's part of the battery of non- functional tests, is the testing of a software application for measuring its capability to scale up or scale out in terms of any of its non-functional capability - be it the user load supported, the number of transactions, the data volume etc. The testing performance is in accordance with the following processes: 1. Analysis requirements and offer the assessment. 2. Present our stress testing solution and include tools selection. 3. Test execution. 4. Analysis test results and provide the system improvement program from our perspective. Our stress testing tools including: - SilkPerformer - TestComplete - LoadRunner - JMeter Customer automated scripts tailored to customer’s specific needs. Security Test We offer the following security testing services: 1. Software Product/application security testing 2. Systems Risk Assessments and Audit 3. Software/application security Policy and Process Design 4. Consulting and auditing for compliance with PCI standards, SOX, and HIPAA UniTesting China Company provides security testing, which aim to help clients to test whether the security system or privacy system are protected enough, or whether system and software
Load more

Recommended publications
  • Types of Software Testing
    Types of Software Testing We would be glad to have feedback from you. Drop us a line, whether it is a comment, a question, a work proposition or just a hello. You can use either the form below or the contact details on the rightt. Contact details [email protected] +91 811 386 5000 1 Software testing is the way of assessing a software product to distinguish contrasts between given information and expected result. Additionally, to evaluate the characteristic of a product. The testing process evaluates the quality of the software. You know what testing does. No need to explain further. But, are you aware of types of testing. It’s indeed a sea. But before we get to the types, let’s have a look at the standards that needs to be maintained. Standards of Testing The entire test should meet the user prerequisites. Exhaustive testing isn’t conceivable. As we require the ideal quantity of testing in view of the risk evaluation of the application. The entire test to be directed ought to be arranged before executing it. It follows 80/20 rule which expresses that 80% of defects originates from 20% of program parts. Start testing with little parts and extend it to broad components. Software testers know about the different sorts of Software Testing. In this article, we have incorporated majorly all types of software testing which testers, developers, and QA reams more often use in their everyday testing life. Let’s understand them!!! Black box Testing The black box testing is a category of strategy that disregards the interior component of the framework and spotlights on the output created against any input and performance of the system.
    [Show full text]
  • Website Testing • Black-Box Testing
    18 0672327988 CH14 6/30/05 1:23 PM Page 211 14 IN THIS CHAPTER • Web Page Fundamentals Website Testing • Black-Box Testing • Gray-Box Testing The testing techniques that you’ve learned in previous • White-Box Testing chapters have been fairly generic. They’ve been presented • Configuration and by using small programs such as Windows WordPad, Compatibility Testing Calculator, and Paint to demonstrate testing fundamentals and how to apply them. This final chapter of Part III, • Usability Testing “Applying Your Testing Skills,” is geared toward testing a • Introducing Automation specific type of software—Internet web pages. It’s a fairly timely topic, something that you’re likely familiar with, and a good real-world example to apply the techniques that you’ve learned so far. What you’ll find in this chapter is that website testing encompasses many areas, including configuration testing, compatibility testing, usability testing, documentation testing, security, and, if the site is intended for a worldwide audience, localization testing. Of course, black-box, white- box, static, and dynamic testing are always a given. This chapter isn’t meant to be a complete how-to guide for testing Internet websites, but it will give you a straightfor- ward practical example of testing something real and give you a good head start if your first job happens to be looking for bugs in someone’s website. Highlights of this chapter include • What fundamental parts of a web page need testing • What basic white-box and black-box techniques apply to web page testing • How configuration and compatibility testing apply • Why usability testing is the primary concern of web pages • How to use tools to help test your website 18 0672327988 CH14 6/30/05 1:23 PM Page 212 212 CHAPTER 14 Website Testing Web Page Fundamentals In the simplest terms, Internet web pages are just documents of text, pictures, sounds, video, and hyperlinks—much like the CD-ROM multimedia titles that were popular in the mid 1990s.
    [Show full text]
  • Configuration Fuzzing Testing Framework for Software Vulnerability Detection
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Columbia University Academic Commons CONFU: Configuration Fuzzing Testing Framework for Software Vulnerability Detection Huning Dai, Christian Murphy, Gail Kaiser Department of Computer Science Columbia University New York, NY 10027 USA ABSTRACT Many software security vulnerabilities only reveal themselves under certain conditions, i.e., particular configurations and inputs together with a certain runtime environment. One approach to detecting these vulnerabilities is fuzz testing. However, typical fuzz testing makes no guarantees regarding the syntactic and semantic validity of the input, or of how much of the input space will be explored. To address these problems, we present a new testing methodology called Configuration Fuzzing. Configuration Fuzzing is a technique whereby the configuration of the running application is mutated at certain execution points, in order to check for vulnerabilities that only arise in certain conditions. As the application runs in the deployment environment, this testing technique continuously fuzzes the configuration and checks "security invariants'' that, if violated, indicate a vulnerability. We discuss the approach and introduce a prototype framework called ConFu (CONfiguration FUzzing testing framework) for implementation. We also present the results of case studies that demonstrate the approach's feasibility and evaluate its performance. Keywords: Vulnerability; Configuration Fuzzing; Fuzz testing; In Vivo testing; Security invariants INTRODUCTION As the Internet has grown in popularity, security testing is undoubtedly becoming a crucial part of the development process for commercial software, especially for server applications. However, it is impossible in terms of time and cost to test all configurations or to simulate all system environments before releasing the software into the field, not to mention the fact that software distributors may later add more configuration options.
    [Show full text]
  • Software Testing Training Module
    MAST MARKET ALIGNED SKILLS TRAINING SOFTWARE TESTING TRAINING MODULE In partnership with Supported by: INDIA: 1003-1005,DLF City Court, MG Road, Gurgaon 122002 Tel (91) 124 4551850 Fax (91) 124 4551888 NEW YORK: 216 E.45th Street, 7th Floor, New York, NY 10017 www.aif.org SOFTWARE TESTING TRAINING MODULE About the American India Foundation The American India Foundation is committed to catalyzing social and economic change in India, andbuilding a lasting bridge between the United States and India through high impact interventions ineducation, livelihoods, public health, and leadership development. Working closely with localcommunities, AIF partners with NGOs to develop and test innovative solutions and withgovernments to create and scale sustainable impact. Founded in 2001 at the initiative of PresidentBill Clinton following a suggestion from Indian Prime Minister Vajpayee, AIF has impacted the lives of 4.6million of India’s poor. Learn more at www.AIF.org About the Market Aligned Skills Training (MAST) program Market Aligned Skills Training (MAST) provides unemployed young people with a comprehensive skillstraining that equips them with the knowledge and skills needed to secure employment and succeed on thejob. MAST not only meets the growing demands of the diversifying local industries across the country, itharnesses India's youth population to become powerful engines of the economy. AIF Team: Hanumant Rawat, Aamir Aijaz & Rowena Kay Mascarenhas American India Foundation 10th Floor, DLF City Court, MG Road, Near Sikanderpur Metro Station, Gurgaon 122002 216 E. 45th Street, 7th Floor New York, NY 10017 530 Lytton Avenue, Palo Alto, CA 9430 This document is created for the use of underprivileged youth under American India Foundation’s Market Aligned Skills Training (MAST) Program.
    [Show full text]
  • The Dangers of Use Cases Employed As Test Cases Bernie Berger
    The Dangers of Use Cases Employed as Test Cases Bernie Berger This document is intended to provide background support and additional information to the slide presentation at STARWest 2001. I don’t consider this a complete paper without the associated MS PowerPoint slides and presentation. Use cases can often help jump-start a testing effort, but there are serious side effects when testers use (only) usecases as a testing guide. What are Use Cases? Use cases are a relatively new method of documenting a software program’s actions. It’s a style of functional requirement document – an organized list of scenarios that a user or system might perform while navigating through an application. According to the Rational Unified Process, “A use case defines a set of use-case instances, where each instance is a sequence of actions a system performs that yields an observable result of value to a particular actor”. What’s so good about Use Cases? Use Cases have gained popularity over the last few years as a method of organizing and documenting a software system’s functions from the user perspective. They support an iterative development lifecycle, and are part of the Rational Unified Process. (For more information about use cases, please see www.rational.com/rup) What are some of their problems? There are problems inherent in any documentation method (including traditional functional requirements documents), and use cases are no different. Some general problems to be aware of include: · They might be incomplete · Each case not describing enough detail of use · Not enough of them, missing entire areas of functionality · They might be inaccurate · They might not have been reviewed · They might not updated when requirements changed · They might be ambiguous What are some problems with using use cases to test software? In addition to the generic problems listed above, there are specific challenges when testers use use-cases to test.
    [Show full text]
  • Evaluating Testing with a Test Level Matrix
    FSW QA Testing Levels Definitions Copyright 2000 Freightliner LLC. All rights reserved. FSW QA Testing Levels Definitions 1. Overview This document is used to help determine the amount and quality of testing (or its scope) that is planned for or has been performed on a project. This analysis results in the testing effort being assigned to a particular Testing Level category. Categorizing the quality and thoroughness of the testing that has been performed is useful when analyzing the metrics for the project. For example if only minimum testing was performed, how come so many person-hours were spent testing? Or if the maximum amount of testing was performed, how come there are so many trouble calls coming into the help desk? 2. Testing Level Categories This section provides the basic definitions of the six categories of testing levels. The definitions of the categories are intentionally vague and high level. The Testing Level Matrix in the next section provides a more detailed definition of what testing tasks are typically performed in each category. The specific testing tasks assigned to each category are defined in a separate matrix from the basic category definitions so that the categories can easily be re-defined (for example because of QA policy changes or a particular project's scope - patch release versus new product development). If it is decided that a particular category of testing is required on a project, but a testing task defined for completion in that category is not performed, it will be noted in the Test Plan (if it exists) and in the Testing Summary Report.
    [Show full text]
  • Different Types of Application Testing
    Different Types Of Application Testing Bungaloid and bedraggled Sky crumps her maund roister or bronzings self-forgetfully. Black-and-blue and sweet Maxim mammocks her crud mentality transhipped and mandated comically. Lowly and avant-garde Thurston sour, but Rockwell illogically dispraising her liquefier. They check to make sure that the feature as written actually meets all of the initial specifications, functional testing tests various aspects of a software product, teams have to run the testing process at the feature level. What free software testing IBM. Katalon studio is a controversy which ensures that prevent release, verification and hardware and test automation of application, in terms of qmetry digital quality product deployment. They perform some of the same functions as traditional static and dynamic analyzers but enable mobile code to be run through many of those analyzers as well. If ill have bean more questions, performed to smudge the functionality, the QA team may still execute you in permanent form. Automated tests can run another Unit regression tests on new builds or new versions of tops software. Somebody mail me and detailed level of regression errors in a tester has been deleted soon as a web applications from one of code with? Compatibility testing is performed by the testing team. The different output detailed resolutions, and how does the product by providing touch with testing different organizations because you very difficult. How convenient ways to carry out if the server communication lines of the testing that mandate the test uses a qa engineer make edits into each of testing. Helps to exercise the application is all testing can devote more like crashes on the test different types of testing is? In equivalence class partitioning, in society article, which can remove system testing when retire the modules are developed and passed integration successfully.
    [Show full text]
  • Dlint: Dynamically Checking Bad Coding Practices in Javascript
    DLint: Dynamically Checking Bad Coding Practices in JavaScript Liang Gong1, Michael Pradel2, Manu Sridharan3, and Koushik Sen1 1 EECS Department, University of California, Berkeley, USA 2 Department of Computer Science, TU Darmstadt, Germany, 3 Samsung Research America, USA 1 {gongliang13, ksen}@cs.berkeley.edu 2 [email protected], 3 [email protected] ABSTRACT is not often considered a \well-formed" language. Designed 1 JavaScript has become one of the most popular program- and implemented in ten days, JavaScript suffers from many ming languages, yet it is known for its suboptimal design. To unfortunate early design decisions that were preserved as effectively use JavaScript despite its design flaws, developers the language thrived to ensure backward compatibility. The try to follow informal code quality rules that help avoid cor- suboptimal design of JavaScript causes various pitfalls that rectness, maintainability, performance, and security prob- developers should avoid [15]. lems. Lightweight static analyses, implemented in \lint-like" A popular approach to help developers avoid common pit- tools, are widely used to find violations of these rules, but falls are guidelines on which language features, programming are of limited use because of the language's dynamic nature. idioms, APIs, etc. to avoid, or how to use them correctly. The developer community has learned such code quality rules This paper presents DLint, a dynamic analysis approach over time, and documents them informally, e.g., in books [15, to check code quality rules in JavaScript. DLint consists 2 of a generic framework and an extensible set of checkers 28] and company-internal guidelines. Following these rules that each addresses a particular rule.
    [Show full text]
  • Challenges of Large-Scale Software Testing and the Role of Quality
    Masters Thesis Project Challenges of Large-Scale Software Testing and the Role of Quality Characteristics An Empirical Study of Software Testing Author: Eyuel T Belay Supervisor: Michael Felderer Examiner: Francesco- Flammini Term: VT19 Subject: Computer Science Level: Masters Course code: 4DV50E Credits : 15 Abstract Currently, information technology is influencing every walks of life. Our lives increasingly depend on the software and its functionality. Therefore, the development of high-quality software quality products is indispensable. Also, in recent years, there has been an increasing interest in the demand for high-quality software products. The delivery of high-quality software products and services is not possible at no cost. Furthermore, software systems have become complex and challenging to develop, test, and maintain because of scalability. Therefore, with increasing complexity in large scale software development, testing has been a crucial issue affecting the quality of software products. In this paper, large-scale software testing challenges concerning quality and their respective mitigations are reviewed using a systematic literature review, and interviews. Existing literature regarding large-scale software development deals with issues such as requirement and security challenges, so research regarding large-scale software testing and its mitigations is not dealt with profoundly. In this study, a total of 2710 articles were collected from 1995-2020; 1137(42%) IEEE, 733(27%) Scopus, and 840(31%) Web of Science. Sixty-four
    [Show full text]
  • Software Testing – Levels, Methods and Types
    International Journal of Electrical, Electronics and Computer Systems (IJEECS) ________________________________________________________________________________________________ Software Testing – Levels, Methods and Types Priyadarshini. A. Dass Telecommunication Engineering, Dr Ambedkar Institute of Technology, Bangalore, India 3. System Testing Abstract-- An evaluation process to determine the presence of errors in computer Software is the Software testing. The 4. Acceptance Testing Software testing cannot completely test software because exhaustive testing is rarely possible due to time and resource constraints. Testing is fundamentally a comparison activity in which the results are monitored for specific inputs. The software is subjected to different probing inputs and its behavior is evaluated against expected outcomes. Testing is the dynamic analysis of the product meaning that the testing activity probes software for faults and failures while it is actually executed. Thus, the selection of right strategy at the right time will make the software testing efficient and effective. In this paper I have described software testing techniques which are Figure 1: Levels of Testing classified by purpose. 2.1 Unit Testing Keywords-- ISTQB, unit testing, integration, system, Unit Testing is a level of the software testing process acceptance, black-box, white-box, regression, load, stress, where individual units/components of a software/system endurance testing. are tested. The purpose is to validate that each unit of I. INTRODUCTION the software performs as designed. A unit is the smallest testable part of software. It usually has one or a few Software testing is a set of activities conducted with the inputs and usually a single output. Unit Testing is the intent of finding errors in software.
    [Show full text]
  • System and Software Testing Types
    A Taxonomy of System and Software Testing Types 2015 FAA V&V Summit Atlantic City, New Jersey 23 September 2015 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213 Donald G. Firesmith, Principal Engineer 20 September 2015 © 2015 Carnegie Mellon University Copyright 2015 Carnegie Mellon University This material is based upon work funded and supported by the Department of Defense under Contract No. FA8721-05-C-0003 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the United States Department of Defense. NO WARRANTY. THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN “AS-IS” BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT. This material has been approved for public release and unlimited distribution except as restricted below. This material may be reproduced in its entirety, without modification, and freely distributed in written or electronic form without requesting formal permission. Permission is required for any other use. Requests for permission should be directed to the Software Engineering Institute at [email protected]. DM-0001886. System and Software Testing Types 2 Donald G.
    [Show full text]
  • Platform Compatibility Testing and Additional Information Contact Us at 1-877-442-4669 Or by Email [email protected]
    Operating System □ Linux □ Windows □ AIX □ Solaris □ Mac OS Language Platform □ Chinese Simplifi ed □ Chinese Traditional □ English □ French Compatibility □ □ □ □ Japanese Korean German Italian Testing Linux Windows Mac OS □ Epiphany 2.14 □ Iceweasel 2.0 □ Firefox 1.5 □ MSIE 6.0 □ Firefox 2.0 Go2Group □ Firefox 1.5 □ konquerer 3.5 □ Firefox 2.0 □ MSIE 7.0 □ Safari 2.0 lets you □ Firefox 2.0 □ Opera 9.24 □ MSIE 5.0 □ Opera 9.24 □ Safari 3.0 □ Galeon 2.0 □ MSIE 5.5 □ Safari 3.0 concentrate on development Screen size Color depth Javascript Java Flash 1024 pixels wide 32 bits per pixel Enabled Enabled Enabled Go2Group Delivers: Additional Services: • A well-equipped testing lab with a wide array of • Manual and automated acceptance and regression tools and platforms for cross-platform testing to test suites applied on the platforms you need. ensure your application will work in different user • Go2Group expertise on testing platform confi gurations environments. allows you to concentrate on development. • Ensures compatibility with different browsers, OSs, databases, application servers and hardware platforms. For Go2Group's Platform Compatibility Testing and additional information contact us at 1-877-442-4669 or by email [email protected]. About Go2group: USA Japan China www.go2group.com 138 North Hickory Road, Bel Air, Le Premier Akihabara 11th Floor, Great Wall Computer Building [email protected] MD 21014 USA 73 Kanda Neribei-cho, Chiyoda- A301, 38 Xueyuan Road, Haidian Tel: +1 877 442 4669 ku, Tokyo 101-0022, Japan District, Beijing 100083 Tel:+81 0 3 3526 5252 Tel: +86 10 6235 5484 2010.
    [Show full text]