Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
public:gsoc:ccextractor_regression_testing [2016/08/08 16:38]
willem [CCExtractor regresssion testing / GitHub bot]
public:gsoc:ccextractor_regression_testing [2018/08/11 18:20]
bashtech
Line 25: Line 25:
  
 This link will take you to the detail page of the test, where you can check the status of the test in general, as well as the results for each category. This link will take you to the detail page of the test, where you can check the status of the test in general, as well as the results for each category.
 +
 +===== How to run your own tests on fork =====
 +
 +If you want to run your own tests on your fork commit with selected regression tests and platforms, Follow these steps:
 +
 +  - Ask for tester/​contributor role from Willem. You can see your role [[https://​sampleplatform.ccextractor.org/​account/​manage|here]].
 +  - After role access, link your github profile in [[https://​sampleplatform.ccextractor.org/​account/​manage|Manage account]] page.
 +  - You can run your own tests [[https://​sampleplatform.ccextractor.org/​custom/​ | here]]. You have to enter commit hash of the fork repository.After that you need to select platforms and regression tests. Test Status is displayed on same page.
  
 ===== Obtaining individual regression samples ===== ===== Obtaining individual regression samples =====
Line 35: Line 43:
 ===== How to use the testing tool manually ===== ===== How to use the testing tool manually =====
  
-If you have access to the dev server at gsocdev.ccextractor.org,​ or have downloaded all the samples, you can run the test tool manually. This has the benefit that you can test just single categories, or specific samples only, whereas the GitHub integration does all the available tests.\\+If you have access to the dev server at gsocdev3.ccextractor.org,​ or have downloaded all the samples, you can run the test tool manually. This has the benefit that you can test just single categories, or specific samples only, whereas the GitHub integration does all the available tests.\\
  
 The easiest way to test all the current samples against your own version of CCExtractor is using a shell script that does most of the work for you:\\ The easiest way to test all the current samples against your own version of CCExtractor is using a shell script that does most of the work for you:\\
 ''​ /​repository/​newRepository/​TestSuite/​runAllTests CCExtractorLocation ReportLocation''​\\ ''​ /​repository/​newRepository/​TestSuite/​runAllTests CCExtractorLocation ReportLocation''​\\
  
-The CCExtractorLocation is the location of your CCExtractor build that you want to test (against the latest official CCX version). The ReportLocation is optional (if omitted, the reports will be stored under your name in [[http://gsocdev.ccextractor.org/​~willem/​users/​|a subfolder of Willem'​s public_html folder]]).\\+The CCExtractorLocation is the location of your CCExtractor build that you want to test (against the latest official CCX version). The ReportLocation is optional (if omitted, the reports will be stored under your name in [[http://gsocdev3.ccextractor.org/​~willem/​users/​|a subfolder of Willem'​s public_html folder]]).\\
  
 If you want to have more configuration options, you can create your own config or test files (there is a sample config at ''/​repository/​newRepository/​TestSuite/​sampleconfig.xml''​ and for a sample test file you can look in the folders), and then call the ccextractortester bash script (located at ''/​repository/​newRepository/​TestSuite/​ccextractortester''​) with the appropriate parameters.\\ If you want to have more configuration options, you can create your own config or test files (there is a sample config at ''/​repository/​newRepository/​TestSuite/​sampleconfig.xml''​ and for a sample test file you can look in the folders), and then call the ccextractortester bash script (located at ''/​repository/​newRepository/​TestSuite/​ccextractortester''​) with the appropriate parameters.\\
  • public/gsoc/ccextractor_regression_testing.txt
  • Last modified: 2018/08/11 18:20
  • by bashtech