毕业设计外文文献—面向大众的Java性能测试.docx

附录A 外文翻译—原文部分 Java Performance Testing For The Masses - Bc. Petr Stefan Analysis To improve the process of performance testing by microbenchmarks, we want to understand the present testing workflow with its strengths and weaknesses first. The data about contemporary and past workflow patterns can be obtained in several ways: ? scanning sources of open-source projects, ? surveying open-source developers, ? surveying software companies, ? analyzing questions about performance on developer websites. Open-source projects allow everyone to view the irsource code an dinvestigate the used frameworks in detail. This allows us to collect the relevant data about how the performance testing frameworks are used in many applications. The major platform for open-source projects is GitHub1, but GitLab2, BitBucket3 or SourceForge4 also have a significant user base. Our choice is to use the biggest platform available. GitHub provides a web API to find projects matching given criteria, so projects using the Java language can be program matically discovered and saved for further processing. The results of a developer survey depend on the willingness of the developers to answer the questionnaire. A crucial part is to target only those developers who made or altered some of the performance tests. They can provide sensible results about how they are testing the performance, how are the results processed, why were the used tools chosen, etc. The questionnaire needs to be fairly short in order not to take too much time from the developers. We made a small survey to complement our knowledge about the open-source testing and to support the results from the GitHub projects. In case of a company survey,we do not believe that we could entice more than a few software corporations to provide meaningful responses with quality results to meet the demands of this text. Similar imprecise results are expected from analyzing questions on QA websites such as StackOverflow5, where the quality dif