<commit_before>fMBT Windows version

Install
-------

* fMBT requires Python 2.7.

* Choose fMBT installer for the same architecture as your Python. If
  you have 32-bit Python 2.7, use fMBT-installer-win32.exe. Print
  Python architecture:

  C:\Python27> python -c "import platform; print platform.architecture()"

* Run fMBT-installer-winXX.exe.

* Let the installer install all (missing) dependencies and allow
  extending PATH.


Build
-----

* Run on Fedora 20:

  ./build-fMBT-installer-winXX.exe.sh 32
  or
  ./build-fMBT-installer-winXX.exe.sh 64

  to produce

  build-win32/fMBT-installer-win32.exe
  or
  build-win64/fMBT-installer-win64.exe.


Status
------

What is expected to work:

* fmbt (test generation and execution)

* fmbt-editor

* fmbt-scripter

* GUI test interfaces: fmbttizen and fmbtwindows


What is likely to have issues (no porting efforts yet):

* GUI test interfaces: fmbtandroid, fmbtchromiumos, fmbtvnc, fmbtrdp


What will not be ported on Windows:

* GUI test interfaces: fmbtx11<commit_msg>doc: Windows support documentation updated<commit_after>fMBT Windows version

Install
-------

* Choose fMBT installer for the same architecture as your Python. If
  you have 32-bit Python 2.7, use fMBT-installer-win32.exe. Print
  Python architecture:

  C:\Python27> python -c "import platform; print platform.architecture()"

  If you do not have Python, the installer that you choose will install
  Python 2.7.8 for the correct architecture, among other dependencies.

* Run fMBT-installer-winXX.exe.

* Let the installer install all (missing) dependencies and allow
  extending PATH.


Build
-----

* Run on Fedora 20:

  ./build-fMBT-installer-winXX.exe.sh 32
  or
  ./build-fMBT-installer-winXX.exe.sh 64

  to produce

  build-win32/fMBT-installer-win32.exe
  or
  build-win64/fMBT-installer-win64.exe.


Status
------

What is expected to work:

* fmbt (test generation and execution)

* fmbt-editor

* fmbt-scripter

* GUI test interfaces:

  - fmbtandroid

  - fmbtchromiumos

  - fmbttizen

  - fmbtwindows


What is likely to have issues (no porting efforts yet):

* GUI test interfaces: fmbtvnc, fmbtrdp


What is not planned to be ported on Windows:

* GUI test interfaces: fmbtx11
{'fraction_non_alphanumeric': 0.09303370786516854, 'fraction_numerical': 0.023820224719101123, 'mean_word_length': 3.330739299610895, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4778955', 'n_tokens_mistral': 844, 'n_tokens_neox': 751, 'n_words': 244}