Diff of the two buildlogs: -- --- b1/build.log 2023-06-08 14:16:48.567017007 +0000 +++ b2/build.log 2023-06-08 14:18:45.505907538 +0000 @@ -1,6 +1,6 @@ I: pbuilder: network access will be disabled during build -I: Current time: Thu Jun 8 02:13:49 -12 2023 -I: pbuilder-time-stamp: 1686233629 +I: Current time: Thu Jul 11 10:39:47 +14 2024 +I: pbuilder-time-stamp: 1720643987 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/bookworm-reproducible-base.tgz] I: copying local configuration @@ -17,7 +17,7 @@ I: copying [./analizo_1.25.4.orig.tar.gz] I: copying [./analizo_1.25.4-2.debian.tar.xz] I: Extracting source -gpgv: Signature made Sat Oct 15 01:20:27 2022 -12 +gpgv: Signature made Sun Oct 16 03:20:27 2022 +14 gpgv: using RSA key D1E1316E93A760A8104D85FABB3A68018649AA06 gpgv: Can't check signature: No public key dpkg-source: warning: cannot verify inline signature for ./analizo_1.25.4-2.dsc: no acceptable signature found @@ -31,137 +31,169 @@ dpkg-source: info: applying no-shell-for-system.patch I: Not using root during the build. I: Installing the build-deps -I: user script /srv/workspace/pbuilder/29568/tmp/hooks/D02_print_environment starting +I: user script /srv/workspace/pbuilder/76205/tmp/hooks/D01_modify_environment starting +debug: Running on ionos16-i386. +I: Changing host+domainname to test build reproducibility +I: Adding a custom variable just for the fun of it... +I: Changing /bin/sh to bash +'/bin/sh' -> '/bin/bash' +lrwxrwxrwx 1 root root 9 Jul 11 10:39 /bin/sh -> /bin/bash +I: Setting pbuilder2's login shell to /bin/bash +I: Setting pbuilder2's GECOS to second user,second room,second work-phone,second home-phone,second other +I: user script /srv/workspace/pbuilder/76205/tmp/hooks/D01_modify_environment finished +I: user script /srv/workspace/pbuilder/76205/tmp/hooks/D02_print_environment starting I: set - BUILDDIR='/build' - BUILDUSERGECOS='first user,first room,first work-phone,first home-phone,first other' - BUILDUSERNAME='pbuilder1' - BUILD_ARCH='i386' - DEBIAN_FRONTEND='noninteractive' - DEB_BUILD_OPTIONS='buildinfo=+all reproducible=+all parallel=8 ' - DISTRIBUTION='bookworm' - HOME='/root' - HOST_ARCH='i386' + BASH=/bin/sh + BASHOPTS=checkwinsize:cmdhist:complete_fullquote:extquote:force_fignore:globasciiranges:globskipdots:hostcomplete:interactive_comments:patsub_replacement:progcomp:promptvars:sourcepath + BASH_ALIASES=() + BASH_ARGC=() + BASH_ARGV=() + BASH_CMDS=() + BASH_LINENO=([0]="12" [1]="0") + BASH_LOADABLES_PATH=/usr/local/lib/bash:/usr/lib/bash:/opt/local/lib/bash:/usr/pkg/lib/bash:/opt/pkg/lib/bash:. + BASH_SOURCE=([0]="/tmp/hooks/D02_print_environment" [1]="/tmp/hooks/D02_print_environment") + BASH_VERSINFO=([0]="5" [1]="2" [2]="15" [3]="1" [4]="release" [5]="i686-pc-linux-gnu") + BASH_VERSION='5.2.15(1)-release' + BUILDDIR=/build + BUILDUSERGECOS='second user,second room,second work-phone,second home-phone,second other' + BUILDUSERNAME=pbuilder2 + BUILD_ARCH=i386 + DEBIAN_FRONTEND=noninteractive + DEB_BUILD_OPTIONS='buildinfo=+all reproducible=+all parallel=15 ' + DIRSTACK=() + DISTRIBUTION=bookworm + EUID=0 + FUNCNAME=([0]="Echo" [1]="main") + GROUPS=() + HOME=/root + HOSTNAME=i-capture-the-hostname + HOSTTYPE=i686 + HOST_ARCH=i386 IFS=' ' - INVOCATION_ID='e7b3bc5107874714a13dfd37418367d2' - LANG='C' - LANGUAGE='en_US:en' - LC_ALL='C' - LD_LIBRARY_PATH='/usr/lib/libeatmydata' - LD_PRELOAD='libeatmydata.so' - MAIL='/var/mail/root' - OPTIND='1' - PATH='/usr/sbin:/usr/bin:/sbin:/bin:/usr/games' - PBCURRENTCOMMANDLINEOPERATION='build' - PBUILDER_OPERATION='build' - PBUILDER_PKGDATADIR='/usr/share/pbuilder' - PBUILDER_PKGLIBDIR='/usr/lib/pbuilder' - PBUILDER_SYSCONFDIR='/etc' - PPID='29568' - PS1='# ' - PS2='> ' + INVOCATION_ID=d75b0e38564f4067a8ba9e4d80e5b7fa + LANG=C + LANGUAGE=de_CH:de + LC_ALL=C + LD_LIBRARY_PATH=/usr/lib/libeatmydata + LD_PRELOAD=libeatmydata.so + MACHTYPE=i686-pc-linux-gnu + MAIL=/var/mail/root + OPTERR=1 + OPTIND=1 + OSTYPE=linux-gnu + PATH=/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path + PBCURRENTCOMMANDLINEOPERATION=build + PBUILDER_OPERATION=build + PBUILDER_PKGDATADIR=/usr/share/pbuilder + PBUILDER_PKGLIBDIR=/usr/lib/pbuilder + PBUILDER_SYSCONFDIR=/etc + PIPESTATUS=([0]="0") + POSIXLY_CORRECT=y + PPID=76205 PS4='+ ' - PWD='/' - SHELL='/bin/bash' - SHLVL='2' - SUDO_COMMAND='/usr/bin/timeout -k 18.1h 18h /usr/bin/ionice -c 3 /usr/bin/nice /usr/sbin/pbuilder --build --configfile /srv/reproducible-results/rbuild-debian/r-b-build.QJCCfJog/pbuilderrc_UxTo --distribution bookworm --hookdir /etc/pbuilder/first-build-hooks --debbuildopts -b --basetgz /var/cache/pbuilder/bookworm-reproducible-base.tgz --buildresult /srv/reproducible-results/rbuild-debian/r-b-build.QJCCfJog/b1 --logfile b1/build.log analizo_1.25.4-2.dsc' - SUDO_GID='112' - SUDO_UID='107' - SUDO_USER='jenkins' - TERM='unknown' - TZ='/usr/share/zoneinfo/Etc/GMT+12' - USER='root' - _='/usr/bin/systemd-run' - http_proxy='http://78.137.99.97:3128' + PWD=/ + SHELL=/bin/bash + SHELLOPTS=braceexpand:errexit:hashall:interactive-comments:posix + SHLVL=3 + SUDO_COMMAND='/usr/bin/timeout -k 24.1h 24h /usr/bin/ionice -c 3 /usr/bin/nice -n 11 /usr/bin/unshare --uts -- /usr/sbin/pbuilder --build --configfile /srv/reproducible-results/rbuild-debian/r-b-build.QJCCfJog/pbuilderrc_xB10 --distribution bookworm --hookdir /etc/pbuilder/rebuild-hooks --debbuildopts -b --basetgz /var/cache/pbuilder/bookworm-reproducible-base.tgz --buildresult /srv/reproducible-results/rbuild-debian/r-b-build.QJCCfJog/b2 --logfile b2/build.log --extrapackages usrmerge analizo_1.25.4-2.dsc' + SUDO_GID=112 + SUDO_UID=107 + SUDO_USER=jenkins + TERM=unknown + TZ=/usr/share/zoneinfo/Etc/GMT-14 + UID=0 + USER=root + _='I: set' + http_proxy=http://85.184.249.68:3128 I: uname -a - Linux ionos12-i386 5.10.0-23-686-pae #1 SMP Debian 5.10.179-1 (2023-05-12) i686 GNU/Linux + Linux i-capture-the-hostname 5.10.0-23-amd64 #1 SMP Debian 5.10.179-1 (2023-05-12) x86_64 GNU/Linux I: ls -l /bin total 6036 - -rwxr-xr-x 1 root root 1408088 Apr 23 09:24 bash - -rwxr-xr-x 3 root root 38404 Sep 18 2022 bunzip2 - -rwxr-xr-x 3 root root 38404 Sep 18 2022 bzcat - lrwxrwxrwx 1 root root 6 Sep 18 2022 bzcmp -> bzdiff - -rwxr-xr-x 1 root root 2225 Sep 18 2022 bzdiff - lrwxrwxrwx 1 root root 6 Sep 18 2022 bzegrep -> bzgrep - -rwxr-xr-x 1 root root 4893 Nov 27 2021 bzexe - lrwxrwxrwx 1 root root 6 Sep 18 2022 bzfgrep -> bzgrep - -rwxr-xr-x 1 root root 3775 Sep 18 2022 bzgrep - -rwxr-xr-x 3 root root 38404 Sep 18 2022 bzip2 - -rwxr-xr-x 1 root root 17892 Sep 18 2022 bzip2recover - lrwxrwxrwx 1 root root 6 Sep 18 2022 bzless -> bzmore - -rwxr-xr-x 1 root root 1297 Sep 18 2022 bzmore - -rwxr-xr-x 1 root root 42920 Sep 20 2022 cat - -rwxr-xr-x 1 root root 79816 Sep 20 2022 chgrp - -rwxr-xr-x 1 root root 67496 Sep 20 2022 chmod - -rwxr-xr-x 1 root root 79816 Sep 20 2022 chown - -rwxr-xr-x 1 root root 162024 Sep 20 2022 cp - -rwxr-xr-x 1 root root 136916 Jan 5 01:20 dash - -rwxr-xr-x 1 root root 137160 Sep 20 2022 date - -rwxr-xr-x 1 root root 100364 Sep 20 2022 dd - -rwxr-xr-x 1 root root 108940 Sep 20 2022 df - -rwxr-xr-x 1 root root 162152 Sep 20 2022 dir - -rwxr-xr-x 1 root root 87760 Mar 22 22:20 dmesg - lrwxrwxrwx 1 root root 8 Dec 19 01:33 dnsdomainname -> hostname - lrwxrwxrwx 1 root root 8 Dec 19 01:33 domainname -> hostname - -rwxr-xr-x 1 root root 38760 Sep 20 2022 echo - -rwxr-xr-x 1 root root 41 Jan 24 02:43 egrep - -rwxr-xr-x 1 root root 34664 Sep 20 2022 false - -rwxr-xr-x 1 root root 41 Jan 24 02:43 fgrep - -rwxr-xr-x 1 root root 84272 Mar 22 22:20 findmnt - -rwsr-xr-x 1 root root 30240 Mar 22 20:38 fusermount - -rwxr-xr-x 1 root root 218680 Jan 24 02:43 grep - -rwxr-xr-x 2 root root 2346 Apr 9 2022 gunzip - -rwxr-xr-x 1 root root 6447 Apr 9 2022 gzexe - -rwxr-xr-x 1 root root 100952 Apr 9 2022 gzip - -rwxr-xr-x 1 root root 21916 Dec 19 01:33 hostname - -rwxr-xr-x 1 root root 75756 Sep 20 2022 ln - -rwxr-xr-x 1 root root 55600 Mar 22 23:43 login - -rwxr-xr-x 1 root root 162152 Sep 20 2022 ls - -rwxr-xr-x 1 root root 214568 Mar 22 22:20 lsblk - -rwxr-xr-x 1 root root 96328 Sep 20 2022 mkdir - -rwxr-xr-x 1 root root 84008 Sep 20 2022 mknod - -rwxr-xr-x 1 root root 38792 Sep 20 2022 mktemp - -rwxr-xr-x 1 root root 63016 Mar 22 22:20 more - -rwsr-xr-x 1 root root 58912 Mar 22 22:20 mount - -rwxr-xr-x 1 root root 13856 Mar 22 22:20 mountpoint - -rwxr-xr-x 1 root root 157932 Sep 20 2022 mv - lrwxrwxrwx 1 root root 8 Dec 19 01:33 nisdomainname -> hostname - lrwxrwxrwx 1 root root 14 Apr 2 18:25 pidof -> /sbin/killall5 - -rwxr-xr-x 1 root root 38792 Sep 20 2022 pwd - lrwxrwxrwx 1 root root 4 Apr 23 09:24 rbash -> bash - -rwxr-xr-x 1 root root 51080 Sep 20 2022 readlink - -rwxr-xr-x 1 root root 75720 Sep 20 2022 rm - -rwxr-xr-x 1 root root 51080 Sep 20 2022 rmdir - -rwxr-xr-x 1 root root 22308 Nov 2 2022 run-parts - -rwxr-xr-x 1 root root 133224 Jan 5 07:55 sed - lrwxrwxrwx 1 root root 4 Jan 5 01:20 sh -> dash - -rwxr-xr-x 1 root root 38760 Sep 20 2022 sleep - -rwxr-xr-x 1 root root 87976 Sep 20 2022 stty - -rwsr-xr-x 1 root root 83492 Mar 22 22:20 su - -rwxr-xr-x 1 root root 38792 Sep 20 2022 sync - -rwxr-xr-x 1 root root 598456 Apr 6 02:25 tar - -rwxr-xr-x 1 root root 13860 Nov 2 2022 tempfile - -rwxr-xr-x 1 root root 120776 Sep 20 2022 touch - -rwxr-xr-x 1 root root 34664 Sep 20 2022 true - -rwxr-xr-x 1 root root 17892 Mar 22 20:38 ulockmgr_server - -rwsr-xr-x 1 root root 30236 Mar 22 22:20 umount - -rwxr-xr-x 1 root root 38760 Sep 20 2022 uname - -rwxr-xr-x 2 root root 2346 Apr 9 2022 uncompress - -rwxr-xr-x 1 root root 162152 Sep 20 2022 vdir - -rwxr-xr-x 1 root root 71216 Mar 22 22:20 wdctl - lrwxrwxrwx 1 root root 8 Dec 19 01:33 ypdomainname -> hostname - -rwxr-xr-x 1 root root 1984 Apr 9 2022 zcat - -rwxr-xr-x 1 root root 1678 Apr 9 2022 zcmp - -rwxr-xr-x 1 root root 6460 Apr 9 2022 zdiff - -rwxr-xr-x 1 root root 29 Apr 9 2022 zegrep - -rwxr-xr-x 1 root root 29 Apr 9 2022 zfgrep - -rwxr-xr-x 1 root root 2081 Apr 9 2022 zforce - -rwxr-xr-x 1 root root 8103 Apr 9 2022 zgrep - -rwxr-xr-x 1 root root 2206 Apr 9 2022 zless - -rwxr-xr-x 1 root root 1842 Apr 9 2022 zmore - -rwxr-xr-x 1 root root 4577 Apr 9 2022 znew -I: user script /srv/workspace/pbuilder/29568/tmp/hooks/D02_print_environment finished + -rwxr-xr-x 1 root root 1408088 Apr 24 2023 bash + -rwxr-xr-x 3 root root 38404 Sep 19 2022 bunzip2 + -rwxr-xr-x 3 root root 38404 Sep 19 2022 bzcat + lrwxrwxrwx 1 root root 6 Sep 19 2022 bzcmp -> bzdiff + -rwxr-xr-x 1 root root 2225 Sep 19 2022 bzdiff + lrwxrwxrwx 1 root root 6 Sep 19 2022 bzegrep -> bzgrep + -rwxr-xr-x 1 root root 4893 Nov 28 2021 bzexe + lrwxrwxrwx 1 root root 6 Sep 19 2022 bzfgrep -> bzgrep + -rwxr-xr-x 1 root root 3775 Sep 19 2022 bzgrep + -rwxr-xr-x 3 root root 38404 Sep 19 2022 bzip2 + -rwxr-xr-x 1 root root 17892 Sep 19 2022 bzip2recover + lrwxrwxrwx 1 root root 6 Sep 19 2022 bzless -> bzmore + -rwxr-xr-x 1 root root 1297 Sep 19 2022 bzmore + -rwxr-xr-x 1 root root 42920 Sep 21 2022 cat + -rwxr-xr-x 1 root root 79816 Sep 21 2022 chgrp + -rwxr-xr-x 1 root root 67496 Sep 21 2022 chmod + -rwxr-xr-x 1 root root 79816 Sep 21 2022 chown + -rwxr-xr-x 1 root root 162024 Sep 21 2022 cp + -rwxr-xr-x 1 root root 136916 Jan 6 2023 dash + -rwxr-xr-x 1 root root 137160 Sep 21 2022 date + -rwxr-xr-x 1 root root 100364 Sep 21 2022 dd + -rwxr-xr-x 1 root root 108940 Sep 21 2022 df + -rwxr-xr-x 1 root root 162152 Sep 21 2022 dir + -rwxr-xr-x 1 root root 87760 Mar 24 2023 dmesg + lrwxrwxrwx 1 root root 8 Dec 20 2022 dnsdomainname -> hostname + lrwxrwxrwx 1 root root 8 Dec 20 2022 domainname -> hostname + -rwxr-xr-x 1 root root 38760 Sep 21 2022 echo + -rwxr-xr-x 1 root root 41 Jan 25 2023 egrep + -rwxr-xr-x 1 root root 34664 Sep 21 2022 false + -rwxr-xr-x 1 root root 41 Jan 25 2023 fgrep + -rwxr-xr-x 1 root root 84272 Mar 24 2023 findmnt + -rwsr-xr-x 1 root root 30240 Mar 23 2023 fusermount + -rwxr-xr-x 1 root root 218680 Jan 25 2023 grep + -rwxr-xr-x 2 root root 2346 Apr 10 2022 gunzip + -rwxr-xr-x 1 root root 6447 Apr 10 2022 gzexe + -rwxr-xr-x 1 root root 100952 Apr 10 2022 gzip + -rwxr-xr-x 1 root root 21916 Dec 20 2022 hostname + -rwxr-xr-x 1 root root 75756 Sep 21 2022 ln + -rwxr-xr-x 1 root root 55600 Mar 24 2023 login + -rwxr-xr-x 1 root root 162152 Sep 21 2022 ls + -rwxr-xr-x 1 root root 214568 Mar 24 2023 lsblk + -rwxr-xr-x 1 root root 96328 Sep 21 2022 mkdir + -rwxr-xr-x 1 root root 84008 Sep 21 2022 mknod + -rwxr-xr-x 1 root root 38792 Sep 21 2022 mktemp + -rwxr-xr-x 1 root root 63016 Mar 24 2023 more + -rwsr-xr-x 1 root root 58912 Mar 24 2023 mount + -rwxr-xr-x 1 root root 13856 Mar 24 2023 mountpoint + -rwxr-xr-x 1 root root 157932 Sep 21 2022 mv + lrwxrwxrwx 1 root root 8 Dec 20 2022 nisdomainname -> hostname + lrwxrwxrwx 1 root root 14 Apr 3 2023 pidof -> /sbin/killall5 + -rwxr-xr-x 1 root root 38792 Sep 21 2022 pwd + lrwxrwxrwx 1 root root 4 Apr 24 2023 rbash -> bash + -rwxr-xr-x 1 root root 51080 Sep 21 2022 readlink + -rwxr-xr-x 1 root root 75720 Sep 21 2022 rm + -rwxr-xr-x 1 root root 51080 Sep 21 2022 rmdir + -rwxr-xr-x 1 root root 22308 Nov 3 2022 run-parts + -rwxr-xr-x 1 root root 133224 Jan 6 2023 sed + lrwxrwxrwx 1 root root 9 Jul 11 10:39 sh -> /bin/bash + -rwxr-xr-x 1 root root 38760 Sep 21 2022 sleep + -rwxr-xr-x 1 root root 87976 Sep 21 2022 stty + -rwsr-xr-x 1 root root 83492 Mar 24 2023 su + -rwxr-xr-x 1 root root 38792 Sep 21 2022 sync + -rwxr-xr-x 1 root root 598456 Apr 7 2023 tar + -rwxr-xr-x 1 root root 13860 Nov 3 2022 tempfile + -rwxr-xr-x 1 root root 120776 Sep 21 2022 touch + -rwxr-xr-x 1 root root 34664 Sep 21 2022 true + -rwxr-xr-x 1 root root 17892 Mar 23 2023 ulockmgr_server + -rwsr-xr-x 1 root root 30236 Mar 24 2023 umount + -rwxr-xr-x 1 root root 38760 Sep 21 2022 uname + -rwxr-xr-x 2 root root 2346 Apr 10 2022 uncompress + -rwxr-xr-x 1 root root 162152 Sep 21 2022 vdir + -rwxr-xr-x 1 root root 71216 Mar 24 2023 wdctl + lrwxrwxrwx 1 root root 8 Dec 20 2022 ypdomainname -> hostname + -rwxr-xr-x 1 root root 1984 Apr 10 2022 zcat + -rwxr-xr-x 1 root root 1678 Apr 10 2022 zcmp + -rwxr-xr-x 1 root root 6460 Apr 10 2022 zdiff + -rwxr-xr-x 1 root root 29 Apr 10 2022 zegrep + -rwxr-xr-x 1 root root 29 Apr 10 2022 zfgrep + -rwxr-xr-x 1 root root 2081 Apr 10 2022 zforce + -rwxr-xr-x 1 root root 8103 Apr 10 2022 zgrep + -rwxr-xr-x 1 root root 2206 Apr 10 2022 zless + -rwxr-xr-x 1 root root 1842 Apr 10 2022 zmore + -rwxr-xr-x 1 root root 4577 Apr 10 2022 znew +I: user script /srv/workspace/pbuilder/76205/tmp/hooks/D02_print_environment finished -> Attempting to satisfy build-dependencies -> Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy @@ -481,7 +513,7 @@ Get: 216 http://deb.debian.org/debian bookworm/main i386 libzmq5 i386 4.3.4-6 [298 kB] Get: 217 http://deb.debian.org/debian bookworm/main i386 libzmq3-dev i386 4.3.4-6 [526 kB] Get: 218 http://deb.debian.org/debian bookworm/main i386 libzmq-ffi-perl all 1.18-2 [31.7 kB] -Fetched 112 MB in 4s (31.0 MB/s) +Fetched 112 MB in 4s (26.8 MB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package netbase. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 19599 files and directories currently installed.) @@ -1374,8 +1406,19 @@ Writing extended state information... Building tag database... -> Finished parsing the build-deps +Reading package lists... +Building dependency tree... +Reading state information... +usrmerge is already the newest version (35). +0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. I: Building the package -I: Running cd /build/analizo-1.25.4/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" HOME="/nonexistent/first-build" dpkg-buildpackage -us -uc -b && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" HOME="/nonexistent/first-build" dpkg-genchanges -S > ../analizo_1.25.4-2_source.changes +I: user script /srv/workspace/pbuilder/76205/tmp/hooks/A99_set_merged_usr starting +Re-configuring usrmerge... +removed '/etc/unsupported-skip-usrmerge-conversion' +The system has been successfully converted. +I: user script /srv/workspace/pbuilder/76205/tmp/hooks/A99_set_merged_usr finished +hostname: Name or service not known +I: Running cd /build/analizo-1.25.4/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path" HOME="/nonexistent/second-build" dpkg-buildpackage -us -uc -b && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path" HOME="/nonexistent/second-build" dpkg-genchanges -S > ../analizo_1.25.4-2_source.changes dpkg-buildpackage: info: source package analizo dpkg-buildpackage: info: source version 1.25.4-2 dpkg-buildpackage: info: source distribution unstable @@ -1400,71 +1443,71 @@ Writing Makefile for Analizo Writing MYMETA.yml and MYMETA.json dh_auto_build - make -j8 + make -j15 make[1]: Entering directory '/build/analizo-1.25.4' cp share/README blib/lib/auto/share/dist/Analizo/README cp share/bash-completion/analizo blib/lib/auto/share/dist/Analizo/bash-completion/analizo +cp lib/Analizo/Batch.pm blib/lib/Analizo/Batch.pm cp lib/Analizo/Metric/AverageMethodLinesOfCode.pm blib/lib/Analizo/Metric/AverageMethodLinesOfCode.pm -cp lib/Analizo/Batch/Runner/Parallel.pm blib/lib/Analizo/Batch/Runner/Parallel.pm -cp lib/Analizo/GlobalMetric/MethodsPerAbstractClass.pm blib/lib/Analizo/GlobalMetric/MethodsPerAbstractClass.pm -cp lib/Analizo/Command.pm blib/lib/Analizo/Command.pm +cp lib/Analizo/Batch/Git.pm blib/lib/Analizo/Batch/Git.pm cp lib/Analizo/GlobalMetric/ChangeCost.pm blib/lib/Analizo/GlobalMetric/ChangeCost.pm -cp lib/Analizo/Batch/Output/CSV.pm blib/lib/Analizo/Batch/Output/CSV.pm -cp lib/Analizo/LanguageFilter.pm blib/lib/Analizo/LanguageFilter.pm -cp lib/Analizo/Metric/AverageNumberOfParameters.pm blib/lib/Analizo/Metric/AverageNumberOfParameters.pm -cp lib/Analizo/Batch/Job/Git.pm blib/lib/Analizo/Batch/Job/Git.pm -cp lib/Analizo/Batch/Job.pm blib/lib/Analizo/Batch/Job.pm +cp lib/Analizo/Batch/Runner/Sequential.pm blib/lib/Analizo/Batch/Runner/Sequential.pm +cp lib/Analizo/Batch/Output.pm blib/lib/Analizo/Batch/Output.pm +cp lib/Analizo/Command/tree_evolution.pm blib/lib/Analizo/Command/tree_evolution.pm +cp lib/Analizo/Command.pm blib/lib/Analizo/Command.pm +cp lib/Analizo/Command/help.pm blib/lib/Analizo/Command/help.pm +cp lib/Analizo/GlobalMetric/MethodsPerAbstractClass.pm blib/lib/Analizo/GlobalMetric/MethodsPerAbstractClass.pm +cp lib/Analizo/Command/metrics_history.pm blib/lib/Analizo/Command/metrics_history.pm cp lib/Analizo/GlobalMetric/TotalAbstractClasses.pm blib/lib/Analizo/GlobalMetric/TotalAbstractClasses.pm -cp lib/Analizo/Metric/AfferentConnections.pm blib/lib/Analizo/Metric/AfferentConnections.pm -cp lib/Analizo/Batch/Job/Directories.pm blib/lib/Analizo/Batch/Job/Directories.pm -cp lib/Analizo/Batch/Runner.pm blib/lib/Analizo/Batch/Runner.pm -cp lib/Analizo/Metric/AverageCycloComplexity.pm blib/lib/Analizo/Metric/AverageCycloComplexity.pm cp lib/Analizo/Batch/Output/DB.pm blib/lib/Analizo/Batch/Output/DB.pm +cp lib/Analizo/Metric/AverageNumberOfParameters.pm blib/lib/Analizo/Metric/AverageNumberOfParameters.pm +cp lib/Analizo/Batch/Directories.pm blib/lib/Analizo/Batch/Directories.pm +cp lib/Analizo/Batch/Runner/Parallel.pm blib/lib/Analizo/Batch/Runner/Parallel.pm +cp lib/Analizo/Command/metrics_batch.pm blib/lib/Analizo/Command/metrics_batch.pm cp lib/Analizo/Command/files_graph.pm blib/lib/Analizo/Command/files_graph.pm -cp lib/Analizo/Extractor/Doxyparse.pm blib/lib/Analizo/Extractor/Doxyparse.pm -cp lib/Analizo/Batch/Runner/Sequential.pm blib/lib/Analizo/Batch/Runner/Sequential.pm -cp lib/Analizo/Batch/Output.pm blib/lib/Analizo/Batch/Output.pm cp lib/Analizo/Command/graph.pm blib/lib/Analizo/Command/graph.pm -cp lib/Analizo/Batch/Directories.pm blib/lib/Analizo/Batch/Directories.pm -cp lib/Analizo/Extractor.pm blib/lib/Analizo/Extractor.pm -cp lib/Analizo/Command/metrics.pm blib/lib/Analizo/Command/metrics.pm +cp lib/Analizo/Metric/AverageCycloComplexity.pm blib/lib/Analizo/Metric/AverageCycloComplexity.pm cp lib/Analizo.pm blib/lib/Analizo.pm -cp lib/Analizo/Filter/Client.pm blib/lib/Analizo/Filter/Client.pm -cp lib/Analizo/Batch.pm blib/lib/Analizo/Batch.pm -cp lib/Analizo/Command/help.pm blib/lib/Analizo/Command/help.pm -cp lib/Analizo/Command/tree_evolution.pm blib/lib/Analizo/Command/tree_evolution.pm +cp lib/Analizo/Batch/Output/CSV.pm blib/lib/Analizo/Batch/Output/CSV.pm cp lib/Analizo/FilenameFilter.pm blib/lib/Analizo/FilenameFilter.pm -cp lib/Analizo/Command/metrics_batch.pm blib/lib/Analizo/Command/metrics_batch.pm -cp lib/Analizo/Batch/Git.pm blib/lib/Analizo/Batch/Git.pm +cp lib/Analizo/Metric/AfferentConnections.pm blib/lib/Analizo/Metric/AfferentConnections.pm +cp lib/Analizo/Command/metrics.pm blib/lib/Analizo/Command/metrics.pm +cp lib/Analizo/Extractor.pm blib/lib/Analizo/Extractor.pm +cp lib/Analizo/Batch/Job.pm blib/lib/Analizo/Batch/Job.pm +cp lib/Analizo/Batch/Runner.pm blib/lib/Analizo/Batch/Runner.pm +cp lib/Analizo/Batch/Job/Directories.pm blib/lib/Analizo/Batch/Job/Directories.pm cp lib/Analizo/GlobalMetrics.pm blib/lib/Analizo/GlobalMetrics.pm -cp lib/Analizo/Command/metrics_history.pm blib/lib/Analizo/Command/metrics_history.pm -cp lib/Test/Analizo/BDD/Cucumber/Extension.pm blib/lib/Test/Analizo/BDD/Cucumber/Extension.pm -cp lib/Analizo/Metric/MaximumMethodLinesOfCode.pm blib/lib/Analizo/Metric/MaximumMethodLinesOfCode.pm +cp lib/Analizo/LanguageFilter.pm blib/lib/Analizo/LanguageFilter.pm +cp lib/Analizo/Filter/Client.pm blib/lib/Analizo/Filter/Client.pm +cp lib/Analizo/Extractor/Doxyparse.pm blib/lib/Analizo/Extractor/Doxyparse.pm +cp lib/Analizo/Batch/Job/Git.pm blib/lib/Analizo/Batch/Job/Git.pm +cp profile.pl blib/lib/profile.pl +cp lib/Analizo/Metric/NumberOfMethods.pm blib/lib/Analizo/Metric/NumberOfMethods.pm +cp lib/Analizo/Metric/ResponseForClass.pm blib/lib/Analizo/Metric/ResponseForClass.pm cp lib/Test/Analizo/Class.pm blib/lib/Test/Analizo/Class.pm -cp lib/Analizo/Metric/StructuralComplexity.pm blib/lib/Analizo/Metric/StructuralComplexity.pm +cp lib/Analizo/Metric/LackOfCohesionOfMethods.pm blib/lib/Analizo/Metric/LackOfCohesionOfMethods.pm +cp lib/Analizo/ModuleMetric.pm blib/lib/Analizo/ModuleMetric.pm +cp lib/Analizo/Metric/MaximumMethodLinesOfCode.pm blib/lib/Analizo/Metric/MaximumMethodLinesOfCode.pm +cp lib/Analizo/Metric/NumberOfPublicMethods.pm blib/lib/Analizo/Metric/NumberOfPublicMethods.pm +cp lib/Analizo/Metric/NumberOfChildren.pm blib/lib/Analizo/Metric/NumberOfChildren.pm +cp lib/Test/Analizo/BDD/Cucumber/Extension.pm blib/lib/Test/Analizo/BDD/Cucumber/Extension.pm cp lib/Analizo/Metric/NumberOfPublicAttributes.pm blib/lib/Analizo/Metric/NumberOfPublicAttributes.pm -cp lib/Analizo/Metric/CouplingBetweenObjects.pm blib/lib/Analizo/Metric/CouplingBetweenObjects.pm -cp lib/Test/Analizo/Git.pm blib/lib/Test/Analizo/Git.pm -cp lib/Analizo/Metric/DepthOfInheritanceTree.pm blib/lib/Analizo/Metric/DepthOfInheritanceTree.pm cp lib/Analizo/Metrics.pm blib/lib/Analizo/Metrics.pm -cp lib/Analizo/Metric/ResponseForClass.pm blib/lib/Analizo/Metric/ResponseForClass.pm -cp lib/Analizo/Metric/LinesOfCode.pm blib/lib/Analizo/Metric/LinesOfCode.pm -cp lib/Analizo/Metric/NumberOfPublicMethods.pm blib/lib/Analizo/Metric/NumberOfPublicMethods.pm -cp lib/Test/Analizo.pm blib/lib/Test/Analizo.pm +cp lib/Analizo/Metric/CouplingBetweenObjects.pm blib/lib/Analizo/Metric/CouplingBetweenObjects.pm +cp lib/Analizo/Metric/StructuralComplexity.pm blib/lib/Analizo/Metric/StructuralComplexity.pm +cp lib/Analizo/Model.pm blib/lib/Analizo/Model.pm cp lib/Analizo/ModuleMetrics.pm blib/lib/Analizo/ModuleMetrics.pm -cp lib/Analizo/Metric/NumberOfChildren.pm blib/lib/Analizo/Metric/NumberOfChildren.pm +cp lib/Test/Analizo.pm blib/lib/Test/Analizo.pm cp lib/Analizo/Metric/NumberOfAttributes.pm blib/lib/Analizo/Metric/NumberOfAttributes.pm -cp lib/Analizo/Model.pm blib/lib/Analizo/Model.pm -cp lib/Analizo/ModuleMetric.pm blib/lib/Analizo/ModuleMetric.pm -cp lib/Analizo/Metric/LackOfCohesionOfMethods.pm blib/lib/Analizo/Metric/LackOfCohesionOfMethods.pm -cp profile.pl blib/lib/profile.pl -cp lib/Analizo/Metric/NumberOfMethods.pm blib/lib/Analizo/Metric/NumberOfMethods.pm +cp lib/Analizo/Metric/DepthOfInheritanceTree.pm blib/lib/Analizo/Metric/DepthOfInheritanceTree.pm +cp lib/Test/Analizo/Git.pm blib/lib/Test/Analizo/Git.pm +cp lib/Analizo/Metric/LinesOfCode.pm blib/lib/Analizo/Metric/LinesOfCode.pm cp bin/analizo blib/script/analizo "/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/analizo Manifying 26 pod documents make[1]: Leaving directory '/build/analizo-1.25.4' dh_auto_test - make -j8 test TEST_VERBOSE=1 + make -j15 test TEST_VERBOSE=1 make[1]: Entering directory '/build/analizo-1.25.4' Skip blib/lib/auto/share/dist/Analizo/README (unchanged) Skip blib/lib/auto/share/dist/Analizo/bash-completion/analizo (unchanged) @@ -1551,8 +1594,8 @@ ok 8 - must not analyze commit containing only (prog.cc) ok 9 - must not analyze commit containing only (prog.cc) ok 10 - must not analyze commit containing only (prog.cc) -ok 11 - must not analyze commit containing only (prog.cc,output.cc,output.h) -ok 12 - must not analyze commit containing only (prog.cc,input.h,input.cc) +ok 11 - must not analyze commit containing only (output.h,prog.cc,output.cc) +ok 12 - must not analyze commit containing only (input.cc,prog.cc,input.h) ok 13 - must not analyze commit containing only (prog.cc) ok 14 - find commit ok 15 - An object of class 'Analizo::Batch::Job::Git' isa 'Analizo::Batch::Job::Git' @@ -2880,954 +2923,954 @@ t/author-pod-spell.t ..................................................... skipped: these tests are for testing by the author t/author-pod-syntax.t .................................................... skipped: these tests are for testing by the author t/features.t ............................................................. -# Feature storing VCS data in a database -# As a software engineering researcher I want to store data about the changes in a project So that I can analyze the development process -# Scenario basics -ok 1 - When I explode t/samples/evolution.tar.gz -# -ok 2 - And I run "analizo metrics-history -f db -o data.db" +# Feature loading command line options from .analizo +# As a analizo user I want to store command line options in a file called .analizo inside my project So that I don't need to alway pass all those options on the command line +# Scenario analizo metrics +ok 1 - Given I copy t/samples/mixed into a temporary directory # -ok 3 - Then the exit status must be 0 +ok 2 - And I create a file called .analizo with the following content +# """metrics: --language java""" +ok 3 - When I run "analizo metrics ." # -ok 4 - When I run "select * from modules" on database "data.db" +ok 4 - Then the output must not match "native_backend.c" # -ok 5 - Then the output must match "Input" +ok 5 - And the output must match "UI.java" # -ok 6 - And the output must match "Output" +ok 6 - And the exit status must be 0 # -ok 7 - And the output must match "prog" +# Scenario all others +ok 7 - Given I change to an empty temporary directory # -# Feature exclude directories from the analysis -# As a software developer in a large project I want to exclude some directories from the source code analysis In order to not analyse non-production code such as tests -# Scenario excluding test directory -ok 8 - Given I am in t/samples/multidir/cpp +ok 8 - And I create a file called .analizo with the following content +# """: --help""" +ok 9 - When I run "analizo graph" # -ok 9 - When I run "analizo metrics --exclude test ." +ok 10 - Then the output must match "analizo graph is part of the analizo suite." # -ok 10 - Then the output must match "module: HelloWorld" +# Scenario all others +ok 11 - Given I change to an empty temporary directory # -ok 11 - And the output must not match "module: hello_test" +ok 12 - And I create a file called .analizo with the following content +# """: --help""" +ok 13 - When I run "analizo metrics" # -# Scenario excluding test directory -ok 12 - Given I am in t/samples/multidir/csharp +ok 14 - Then the output must match "analizo metrics is part of the analizo suite." # -ok 13 - When I run "analizo metrics --exclude test ." +# Scenario all others +ok 15 - Given I change to an empty temporary directory # -ok 14 - Then the output must match "module: HelloWorld" +ok 16 - And I create a file called .analizo with the following content +# """: --help""" +ok 17 - When I run "analizo metrics-batch" # -ok 15 - And the output must not match "module: hello_test" +ok 18 - Then the output must match "analizo metrics-batch is part of the analizo suite." # -# Scenario excluding a list of directories -ok 16 - Given I am in t/samples/multidir/cpp +# Scenario all others +ok 19 - Given I change to an empty temporary directory # -ok 17 - When I run "analizo metrics --exclude test:src ." +ok 20 - And I create a file called .analizo with the following content +# """: --help""" +ok 21 - When I run "analizo metrics-history" # -ok 18 - Then the output must not match "module: HelloWorld" +ok 22 - Then the output must match "analizo metrics-history is part of the analizo suite." # -ok 19 - And the output must not match "module: hello_test" +# Scenario all others +ok 23 - Given I change to an empty temporary directory # -# Scenario excluding a list of directories -ok 20 - Given I am in t/samples/multidir/csharp +ok 24 - And I create a file called .analizo with the following content +# """: --help""" +ok 25 - When I run "analizo tree-evolution" # -ok 21 - When I run "analizo metrics --exclude test:src ." +ok 26 - Then the output must match "analizo tree-evolution is part of the analizo suite." # -ok 22 - Then the output must not match "module: HelloWorld" +# Scenario all others +ok 27 - Given I change to an empty temporary directory # -ok 23 - And the output must not match "module: hello_test" +ok 28 - And I create a file called .analizo with the following content +# """: --help""" +ok 29 - When I run "analizo files-graph" # -# Scenario excluding src directory -ok 24 - Given I am in t/samples/multidir/cpp +ok 30 - Then the output must match "analizo files-graph is part of the analizo suite." # -ok 25 - When I run "analizo metrics --exclude src ." +# Scenario all others +ok 31 - Given I change to an empty temporary directory # -ok 26 - Then the output must match "module: hello_test" +ok 32 - And I create a file called .analizo with the following content +# """: --help""" +ok 33 - When I run "analizo help" # -ok 27 - And the output must not match "module: HelloWorld" +ok 34 - Then the output must match "analizo help is part of the analizo suite." # -# Scenario excluding src directory -ok 28 - Given I am in t/samples/multidir/csharp +# Feature doxyparse extractor external tool +# As a Analizo developer I want to guarantee that doxyparse deal with any source code To provide reliability for Analizo users +# Scenario don't die parsing MCLinker.cpp from android 5.1.1 +ok 35 - Given I am in t/samples/android-framework/android-5.1.1_r38 # -ok 29 - When I run "analizo metrics --exclude src ." +ok 36 - When I run "analizo metrics ." # -ok 30 - Then the output must match "module: hello_test" +ok 37 - Then the exit status must be 0 # -ok 31 - And the output must not match "module: HelloWorld" +# Scenario don't duplicate YAML keys parsing AudioTrackShared.cpp from android 5.1.1 +ok 38 - Given I am in t/samples/android-framework/android-5.1.1_r38 # -# Feature metrics batch -# As a software engineering researcher I want to analyze several different projects So I can compare their metrics -# Scenario "hello, world" -ok 32 - Given I am in t/samples/hello_world/ +ok 39 - When I run "analizo metrics ." # -ok 33 - When I run "analizo metrics-batch" +ok 40 - Then analizo must not emit a warning matching "YAML_LOAD_WARN_DUPLICATE_KEY" # -ok 34 - Then the output must match "I: Processed c." +# Scenario don't abort parsing mlpack 3.0.0 +ok 41 - Given I am in t/samples/mlpack-3.0.0 # -ok 35 - And the output must match "I: Processed cpp." +ok 42 - When I run "analizo metrics ." # -ok 36 - And the output must match "I: Processed java." +ok 43 - Then analizo must not emit a warning matching "Aborted" # -# Scenario summarizing -ok 37 - Given I am in t/samples/hello_world/ +ok 44 - And the exit status must be 0 # -ok 38 - When I run "analizo metrics-batch --quiet -o data.csv && cat data.csv && rm -f *.csv" +# Scenario don't die parsing kdelibs warning about unknown escape character +ok 45 - Given I am in t/samples/kdelibs # -ok 39 - Then the output must match "^id," +ok 46 - When I run "analizo metrics ." # -ok 40 - And the output must not match ",---," +ok 47 - Then analizo must not emit a warning matching "Error" # -ok 41 - And the output must match "c," +ok 48 - And the exit status must be 0 # -ok 42 - And the output must match "cpp," +# Scenario don't die parsing mod_suexec.h from http 2.4.38 +ok 49 - Given I am in t/samples/httpd-2.4.38 # -ok 43 - And the output must match "java," +ok 50 - When I run "analizo metrics ." # -ok 44 - And the output must not match "I: Processed" +ok 51 - Then analizo must not emit a warning matching "Not a HASH reference" # -# Scenario support for parallel processing -ok 45 - Given I copy t/samples/hello_world/* into a temporary directory +ok 52 - And the exit status must be 0 # -ok 46 - When I run "analizo metrics-batch -q -o sequential.csv" +# Scenario allow dot on module filename +ok 53 - Given I am in t/samples/sample_basic/c # -ok 47 - And I run "analizo metrics-batch -q -o parallel.csv -p 2" +ok 54 - When I run "analizo metrics ." # -ok 48 - And I run "sort sequential.csv > sequential-sorted.csv" +ok 55 - Then analizo must report that file module1.c declares module module1 # -ok 49 - And I run "sort parallel.csv > parallel-sorted.csv" +# Feature exclude directories from the analysis +# As a software developer in a large project I want to exclude some directories from the source code analysis In order to not analyse non-production code such as tests +# Scenario excluding test directory +ok 56 - Given I am in t/samples/multidir/cpp # -ok 50 - And I run "diff -u sequential-sorted.csv parallel-sorted.csv" +ok 57 - When I run "analizo metrics --exclude test ." # -ok 51 - Then the output must not match "---" +ok 58 - Then the output must match "module: HelloWorld" # -ok 52 - Then the exit status must be 0 +ok 59 - And the output must not match "module: hello_test" # -# Scenario passing two input directories as argument -ok 53 - Given I copy t/samples/hello_world/* into a temporary directory +# Scenario excluding test directory +ok 60 - Given I am in t/samples/multidir/csharp # -ok 54 - When I run "analizo metrics-batch --quiet -o data.csv cpp java" +ok 61 - When I run "analizo metrics --exclude test ." # -ok 55 - Then the exit status must be 0 +ok 62 - Then the output must match "module: HelloWorld" # -ok 56 - And the file "c-details.csv" should not exist +ok 63 - And the output must not match "module: hello_test" # -ok 57 - And the file "cpp-details.csv" should exist +# Scenario excluding a list of directories +ok 64 - Given I am in t/samples/multidir/cpp # -ok 58 - And the file "java-details.csv" should exist +ok 65 - When I run "analizo metrics --exclude test:src ." # -# Scenario passing one input directory as argument -ok 59 - Given I copy t/samples/hello_world/* into a temporary directory +ok 66 - Then the output must not match "module: HelloWorld" # -ok 60 - When I run "analizo metrics-batch --quiet -o data.csv cpp" +ok 67 - And the output must not match "module: hello_test" # -ok 61 - Then the exit status must be 0 +# Scenario excluding a list of directories +ok 68 - Given I am in t/samples/multidir/csharp # -ok 62 - And the file "c-details.csv" should not exist +ok 69 - When I run "analizo metrics --exclude test:src ." # -ok 63 - And the file "cpp-details.csv" should exist +ok 70 - Then the output must not match "module: HelloWorld" # -ok 64 - And the file "java-details.csv" should not exist +ok 71 - And the output must not match "module: hello_test" # -# Feature multi-language support -# As a Researcher or Practioneer I want to be able to analyze software in different languages In order do compare them -# Scenario dependency between modules -ok 65 - Given I am in t/samples/hello_world/c +# Scenario excluding src directory +ok 72 - Given I am in t/samples/multidir/cpp # -ok 66 - When I run "analizo graph --modules ." +ok 73 - When I run "analizo metrics --exclude src ." # -ok 67 - Then analizo must report that "main" depends on "hello_world" +ok 74 - Then the output must match "module: hello_test" # -# Scenario dependency between modules -ok 68 - Given I am in t/samples/hello_world/cpp +ok 75 - And the output must not match "module: HelloWorld" # -ok 69 - When I run "analizo graph --modules ." +# Scenario excluding src directory +ok 76 - Given I am in t/samples/multidir/csharp # -ok 70 - Then analizo must report that "main" depends on "HelloWorld" +ok 77 - When I run "analizo metrics --exclude src ." # -# Scenario dependency between modules -ok 71 - Given I am in t/samples/hello_world/java +ok 78 - Then the output must match "module: hello_test" # -ok 72 - When I run "analizo graph --modules ." +ok 79 - And the output must not match "module: HelloWorld" # -ok 73 - Then analizo must report that "Main" depends on "HelloWorld" +# Feature dependency graph among files +# As a software engineering reasearcher I want to know the all relationships between all files on project So that I can run analizo files-graph to produces a DOT graph from source-code +# Scenario relation between function call +ok 80 - Given I am in t/samples/animals/cpp # -# Scenario dependency between modules -ok 74 - Given I am in t/samples/hello_world/csharp +ok 81 - When I run "analizo files-graph ." # -ok 75 - When I run "analizo graph --modules ." +ok 82 - Then analizo must report that "main" depends on "animal" # -ok 76 - Then analizo must report that "main" depends on "HelloWorld" +# Scenario relation between function call +ok 83 - Given I am in t/samples/animals/java # -# Scenario dependency between specific functions -ok 77 - Given I am in t/samples/hello_world/c +ok 84 - When I run "analizo files-graph ." # -ok 78 - When I run "analizo graph ." +ok 85 - Then analizo must report that "Main" depends on "Animal" # -ok 79 - Then analizo must report that "main::main()" depends on "hello_world::hello_world_say(hello_world *)" +# Scenario relation between function call +ok 86 - Given I am in t/samples/animals/csharp # -ok 80 - And analizo must report that "main::main()" depends on "hello_world::hello_world_destroy(hello_world *)" +ok 87 - When I run "analizo files-graph ." # -# Scenario dependency between specific functions -ok 81 - Given I am in t/samples/hello_world/cpp +ok 88 - Then analizo must report that "Main" depends on "Animal" # -ok 82 - When I run "analizo graph ." +# Scenario relation between inheritance +ok 89 - Given I am in t/samples/animals/cpp # -ok 83 - Then analizo must report that "main::main()" depends on "HelloWorld::say()" +ok 90 - When I run "analizo files-graph ." # -ok 84 - And analizo must report that "main::main()" depends on "HelloWorld::destroy()" +ok 91 - Then analizo must report that "dog" depends on "mammal" # -# Scenario dependency between specific functions -ok 85 - Given I am in t/samples/hello_world/java +# Scenario relation between inheritance +ok 92 - Given I am in t/samples/animals/java # -ok 86 - When I run "analizo graph ." +ok 93 - When I run "analizo files-graph ." # -ok 87 - Then analizo must report that "Main::main(String[])" depends on "HelloWorld::say()" +ok 94 - Then analizo must report that "Dog" depends on "Mammal" # -ok 88 - And analizo must report that "Main::main(String[])" depends on "HelloWorld::destroy()" +# Scenario relation between inheritance +ok 95 - Given I am in t/samples/animals/csharp # -# Scenario dependency between specific functions -ok 89 - Given I am in t/samples/hello_world/csharp +ok 96 - When I run "analizo files-graph ." # -ok 90 - When I run "analizo graph ." +ok 97 - Then analizo must report that "Dog" depends on "Mammal" # -ok 91 - Then analizo must report that "main::Main()" depends on "HelloWorld::say()" +# Scenario relation between inheritance +ok 98 - Given I am in t/samples/animals/cpp # -ok 92 - And analizo must report that "main::Main()" depends on "HelloWorld::destroy()" +ok 99 - When I run "analizo files-graph ." # -# Scenario intra-module dependencies -ok 93 - Given I am in t/samples/hello_world/c +ok 100 - Then analizo must report that "mammal" depends on "animal" # -ok 94 - When I run "analizo graph ." +# Scenario relation between inheritance +ok 101 - Given I am in t/samples/animals/java # -ok 95 - Then analizo must report that "hello_world::hello_world_say(hello_world *)" depends on "hello_world::_hello_world::id" +ok 102 - When I run "analizo files-graph ." # -ok 96 - And analizo must report that "hello_world::hello_world_destroy(hello_world *)" depends on "hello_world::_hello_world::id" +ok 103 - Then analizo must report that "Mammal" depends on "Animal" # -# Scenario intra-module dependencies -ok 97 - Given I am in t/samples/hello_world/cpp +# Scenario relation between inheritance +ok 104 - Given I am in t/samples/animals/csharp # -ok 98 - When I run "analizo graph ." +ok 105 - When I run "analizo files-graph ." # -ok 99 - Then analizo must report that "HelloWorld::say()" depends on "HelloWorld::_id" +ok 106 - Then analizo must report that "Mammal" depends on "Animal" # -ok 100 - And analizo must report that "HelloWorld::destroy()" depends on "HelloWorld::_id" +# Feature multi-language support +# As a Researcher or Practioneer I want to be able to analyze software in different languages In order do compare them +# Scenario dependency between modules +ok 107 - Given I am in t/samples/hello_world/c # -# Scenario intra-module dependencies -ok 101 - Given I am in t/samples/hello_world/java +ok 108 - When I run "analizo graph --modules ." # -ok 102 - When I run "analizo graph ." +ok 109 - Then analizo must report that "main" depends on "hello_world" # -ok 103 - Then analizo must report that "HelloWorld::say()" depends on "HelloWorld::_id" +# Scenario dependency between modules +ok 110 - Given I am in t/samples/hello_world/cpp # -ok 104 - And analizo must report that "HelloWorld::destroy()" depends on "HelloWorld::_id" +ok 111 - When I run "analizo graph --modules ." # -# Scenario intra-module dependencies -ok 105 - Given I am in t/samples/hello_world/csharp +ok 112 - Then analizo must report that "main" depends on "HelloWorld" # -ok 106 - When I run "analizo graph ." +# Scenario dependency between modules +ok 113 - Given I am in t/samples/hello_world/java # -ok 107 - Then analizo must report that "HelloWorld::say()" depends on "HelloWorld::_id" +ok 114 - When I run "analizo graph --modules ." # -ok 108 - And analizo must report that "HelloWorld::destroy()" depends on "HelloWorld::_id" +ok 115 - Then analizo must report that "Main" depends on "HelloWorld" # -# Scenario some metrics -ok 109 - Given I am in t/samples/hello_world/c +# Scenario dependency between modules +ok 116 - Given I am in t/samples/hello_world/csharp # -ok 110 - When I run "analizo metrics ." +ok 117 - When I run "analizo graph --modules ." # -ok 111 - Then analizo must report that the project has total_modules = 2 +ok 118 - Then analizo must report that "main" depends on "HelloWorld" # -ok 112 - And analizo must report that module main has nom = 1 +# Scenario dependency between specific functions +ok 119 - Given I am in t/samples/hello_world/c # -ok 113 - And analizo must report that module hello_world has npm = 3 +ok 120 - When I run "analizo graph ." # -ok 114 - And analizo must report that module hello_world has nom = 3 +ok 121 - Then analizo must report that "main::main()" depends on "hello_world::hello_world_say(hello_world *)" # -ok 115 - And analizo must report that module hello_world has npa = 2 +ok 122 - And analizo must report that "main::main()" depends on "hello_world::hello_world_destroy(hello_world *)" # -# Scenario some metrics -ok 116 - Given I am in t/samples/hello_world/cpp +# Scenario dependency between specific functions +ok 123 - Given I am in t/samples/hello_world/cpp # -ok 117 - When I run "analizo metrics ." +ok 124 - When I run "analizo graph ." # -ok 118 - Then analizo must report that the project has total_modules = 2 +ok 125 - Then analizo must report that "main::main()" depends on "HelloWorld::say()" # -ok 119 - And analizo must report that module main has nom = 1 +ok 126 - And analizo must report that "main::main()" depends on "HelloWorld::destroy()" # -ok 120 - And analizo must report that module HelloWorld has npm = 3 +# Scenario dependency between specific functions +ok 127 - Given I am in t/samples/hello_world/java # -ok 121 - And analizo must report that module HelloWorld has nom = 4 +ok 128 - When I run "analizo graph ." # -ok 122 - And analizo must report that module HelloWorld has npa = 1 +ok 129 - Then analizo must report that "Main::main(String[])" depends on "HelloWorld::say()" # -# Scenario some metrics -ok 123 - Given I am in t/samples/hello_world/java +ok 130 - And analizo must report that "Main::main(String[])" depends on "HelloWorld::destroy()" # -ok 124 - When I run "analizo metrics ." +# Scenario dependency between specific functions +ok 131 - Given I am in t/samples/hello_world/csharp # -ok 125 - Then analizo must report that the project has total_modules = 2 +ok 132 - When I run "analizo graph ." # -ok 126 - And analizo must report that module Main has nom = 1 +ok 133 - Then analizo must report that "main::Main()" depends on "HelloWorld::say()" # -ok 127 - And analizo must report that module HelloWorld has npm = 3 +ok 134 - And analizo must report that "main::Main()" depends on "HelloWorld::destroy()" # -ok 128 - And analizo must report that module HelloWorld has nom = 4 +# Scenario intra-module dependencies +ok 135 - Given I am in t/samples/hello_world/c # -ok 129 - And analizo must report that module HelloWorld has npa = 1 +ok 136 - When I run "analizo graph ." # -# Scenario some metrics -ok 130 - Given I am in t/samples/hello_world/csharp +ok 137 - Then analizo must report that "hello_world::hello_world_say(hello_world *)" depends on "hello_world::_hello_world::id" # -ok 131 - When I run "analizo metrics ." +ok 138 - And analizo must report that "hello_world::hello_world_destroy(hello_world *)" depends on "hello_world::_hello_world::id" # -ok 132 - Then analizo must report that the project has total_modules = 2 +# Scenario intra-module dependencies +ok 139 - Given I am in t/samples/hello_world/cpp # -ok 133 - And analizo must report that module main has nom = 1 +ok 140 - When I run "analizo graph ." # -ok 134 - And analizo must report that module HelloWorld has npm = 3 +ok 141 - Then analizo must report that "HelloWorld::say()" depends on "HelloWorld::_id" # -ok 135 - And analizo must report that module HelloWorld has nom = 4 +ok 142 - And analizo must report that "HelloWorld::destroy()" depends on "HelloWorld::_id" # -ok 136 - And analizo must report that module HelloWorld has npa = 1 +# Scenario intra-module dependencies +ok 143 - Given I am in t/samples/hello_world/java # -# Scenario inheritance data -ok 137 - Given I am in t/samples/animals/cpp +ok 144 - When I run "analizo graph ." # -ok 138 - When I run "analizo graph --modules ." +ok 145 - Then analizo must report that "HelloWorld::say()" depends on "HelloWorld::_id" # -ok 139 - Then analizo must report that "Cat" depends on "Mammal" +ok 146 - And analizo must report that "HelloWorld::destroy()" depends on "HelloWorld::_id" # -ok 140 - And analizo must report that "Dog" depends on "Mammal" +# Scenario intra-module dependencies +ok 147 - Given I am in t/samples/hello_world/csharp # -ok 141 - And analizo must report that "Mammal" depends on "Animal" +ok 148 - When I run "analizo graph ." # -ok 142 - When I run "analizo metrics ." +ok 149 - Then analizo must report that "HelloWorld::say()" depends on "HelloWorld::_id" # -ok 143 - Then analizo must report that module Cat has dit = 2 +ok 150 - And analizo must report that "HelloWorld::destroy()" depends on "HelloWorld::_id" # -ok 144 - And analizo must report that module Dog has dit = 2 +# Scenario some metrics +ok 151 - Given I am in t/samples/hello_world/c # -ok 145 - And analizo must report that module Mammal has dit = 1 +ok 152 - When I run "analizo metrics ." # -ok 146 - And analizo must report that module Animal has dit = 0 +ok 153 - Then analizo must report that the project has total_modules = 2 # -# Scenario inheritance data -ok 147 - Given I am in t/samples/animals/java +ok 154 - And analizo must report that module main has nom = 1 # -ok 148 - When I run "analizo graph --modules ." +ok 155 - And analizo must report that module hello_world has npm = 3 # -ok 149 - Then analizo must report that "Cat" depends on "Mammal" +ok 156 - And analizo must report that module hello_world has nom = 3 # -ok 150 - And analizo must report that "Dog" depends on "Mammal" +ok 157 - And analizo must report that module hello_world has npa = 2 # -ok 151 - And analizo must report that "Mammal" depends on "Animal" +# Scenario some metrics +ok 158 - Given I am in t/samples/hello_world/cpp # -ok 152 - When I run "analizo metrics ." +ok 159 - When I run "analizo metrics ." # -ok 153 - Then analizo must report that module Cat has dit = 2 +ok 160 - Then analizo must report that the project has total_modules = 2 # -ok 154 - And analizo must report that module Dog has dit = 2 +ok 161 - And analizo must report that module main has nom = 1 # -ok 155 - And analizo must report that module Mammal has dit = 1 +ok 162 - And analizo must report that module HelloWorld has npm = 3 # -ok 156 - And analizo must report that module Animal has dit = 0 +ok 163 - And analizo must report that module HelloWorld has nom = 4 # -# Scenario mixed Java and C -ok 157 - Given I am in t/samples/mixed +ok 164 - And analizo must report that module HelloWorld has npa = 1 # -ok 158 - When I run "analizo metrics ." +# Scenario some metrics +ok 165 - Given I am in t/samples/hello_world/java # -ok 159 - Then the output must match "_module: native_backend" +ok 166 - When I run "analizo metrics ." # -ok 160 - And the output must match "_module: UI" +ok 167 - Then analizo must report that the project has total_modules = 2 # -ok 161 - And the output must match "_module: Backend" +ok 168 - And analizo must report that module Main has nom = 1 # -# Feature give manpage on --help -# As a user I want to read the manpage when passing --help command line option In order to get instructions on how to use the tools -# Scenario display manpage for `analizo graph` -ok 162 - When I run "analizo graph --help" +ok 169 - And analizo must report that module HelloWorld has npm = 3 # -ok 163 - Then the output must match "[NAME|N^HNA^HAM^HME^HE]\s+analizo-graph" +ok 170 - And analizo must report that module HelloWorld has nom = 4 # -ok 164 - Then the output must match "[USAGE|U^HUS^HSA^HAG^HGE^HE]\s+analizo graph \[OPTIONS\]" +ok 171 - And analizo must report that module HelloWorld has npa = 1 # -# Scenario display manpage for `analizo metrics` -ok 165 - When I run "analizo metrics --help" -# -ok 166 - Then the output must match "[NAME|N^HNA^HAM^HME^HE]\s+analizo-metrics" -# -ok 167 - Then the output must match "[USAGE|U^HUS^HSA^HAG^HGE^HE]\s+analizo metrics \[OPTIONS\]" +# Scenario some metrics +ok 172 - Given I am in t/samples/hello_world/csharp # -# Scenario display manpage for `analizo metrics-batch` -ok 168 - When I run "analizo metrics-batch --help" +ok 173 - When I run "analizo metrics ." # -ok 169 - Then the output must match "[NAME|N^HNA^HAM^HME^HE]\s+analizo-metrics-batch" +ok 174 - Then analizo must report that the project has total_modules = 2 # -ok 170 - Then the output must match "[USAGE|U^HUS^HSA^HAG^HGE^HE]\s+analizo metrics-batch \[OPTIONS\]" +ok 175 - And analizo must report that module main has nom = 1 # -# Scenario display manpage for `analizo metrics-history` -ok 171 - When I run "analizo metrics-history --help" +ok 176 - And analizo must report that module HelloWorld has npm = 3 # -ok 172 - Then the output must match "[NAME|N^HNA^HAM^HME^HE]\s+analizo-metrics-history" +ok 177 - And analizo must report that module HelloWorld has nom = 4 # -ok 173 - Then the output must match "[USAGE|U^HUS^HSA^HAG^HGE^HE]\s+analizo metrics-history \[OPTIONS\]" +ok 178 - And analizo must report that module HelloWorld has npa = 1 # -# Scenario display manpage for `analizo tree-evolution` -ok 174 - When I run "analizo tree-evolution --help" +# Scenario inheritance data +ok 179 - Given I am in t/samples/animals/cpp # -ok 175 - Then the output must match "[NAME|N^HNA^HAM^HME^HE]\s+analizo-tree-evolution" +ok 180 - When I run "analizo graph --modules ." # -ok 176 - Then the output must match "[USAGE|U^HUS^HSA^HAG^HGE^HE]\s+analizo tree-evolution \[OPTIONS\]" +ok 181 - Then analizo must report that "Cat" depends on "Mammal" # -# Scenario display manpage for `analizo files-graph` -ok 177 - When I run "analizo files-graph --help" +ok 182 - And analizo must report that "Dog" depends on "Mammal" # -ok 178 - Then the output must match "[NAME|N^HNA^HAM^HME^HE]\s+analizo-files-graph" +ok 183 - And analizo must report that "Mammal" depends on "Animal" # -ok 179 - Then the output must match "[USAGE|U^HUS^HSA^HAG^HGE^HE]\s+analizo files-graph \[OPTIONS\]" +ok 184 - When I run "analizo metrics ." # -# Feature dependency graph among files -# As a software engineering reasearcher I want to know the all relationships between all files on project So that I can run analizo files-graph to produces a DOT graph from source-code -# Scenario relation between function call -ok 180 - Given I am in t/samples/animals/cpp +ok 185 - Then analizo must report that module Cat has dit = 2 # -ok 181 - When I run "analizo files-graph ." +ok 186 - And analizo must report that module Dog has dit = 2 # -ok 182 - Then analizo must report that "main" depends on "animal" +ok 187 - And analizo must report that module Mammal has dit = 1 # -# Scenario relation between function call -ok 183 - Given I am in t/samples/animals/java +ok 188 - And analizo must report that module Animal has dit = 0 # -ok 184 - When I run "analizo files-graph ." +# Scenario inheritance data +ok 189 - Given I am in t/samples/animals/java # -ok 185 - Then analizo must report that "Main" depends on "Animal" +ok 190 - When I run "analizo graph --modules ." # -# Scenario relation between function call -ok 186 - Given I am in t/samples/animals/csharp +ok 191 - Then analizo must report that "Cat" depends on "Mammal" # -ok 187 - When I run "analizo files-graph ." +ok 192 - And analizo must report that "Dog" depends on "Mammal" # -ok 188 - Then analizo must report that "Main" depends on "Animal" +ok 193 - And analizo must report that "Mammal" depends on "Animal" # -# Scenario relation between inheritance -ok 189 - Given I am in t/samples/animals/cpp +ok 194 - When I run "analizo metrics ." # -ok 190 - When I run "analizo files-graph ." +ok 195 - Then analizo must report that module Cat has dit = 2 # -ok 191 - Then analizo must report that "dog" depends on "mammal" +ok 196 - And analizo must report that module Dog has dit = 2 # -# Scenario relation between inheritance -ok 192 - Given I am in t/samples/animals/java +ok 197 - And analizo must report that module Mammal has dit = 1 # -ok 193 - When I run "analizo files-graph ." +ok 198 - And analizo must report that module Animal has dit = 0 # -ok 194 - Then analizo must report that "Dog" depends on "Mammal" +# Scenario mixed Java and C +ok 199 - Given I am in t/samples/mixed # -# Scenario relation between inheritance -ok 195 - Given I am in t/samples/animals/csharp +ok 200 - When I run "analizo metrics ." # -ok 196 - When I run "analizo files-graph ." +ok 201 - Then the output must match "_module: native_backend" # -ok 197 - Then analizo must report that "Dog" depends on "Mammal" +ok 202 - And the output must match "_module: UI" # -# Scenario relation between inheritance -ok 198 - Given I am in t/samples/animals/cpp +ok 203 - And the output must match "_module: Backend" # -ok 199 - When I run "analizo files-graph ." +# Feature mapping modules to filenames +# As a software engineering resesearcher I want to know in which file each module is declared So that I can compare that with data from the VCS +# Scenario C++, runing against some directory +ok 204 - When I run "analizo metrics t/samples/animals/cpp" # -ok 200 - Then analizo must report that "mammal" depends on "animal" +ok 205 - Then analizo must report that file animal.h declares module Animal # -# Scenario relation between inheritance -ok 201 - Given I am in t/samples/animals/java +ok 206 - And analizo must report that file cat.cc declares module Cat # -ok 202 - When I run "analizo files-graph ." +ok 207 - And analizo must report that file cat.h declares module Cat # -ok 203 - Then analizo must report that "Mammal" depends on "Animal" +ok 208 - And analizo must report that file cat.cc not declares module Dog # -# Scenario relation between inheritance -ok 204 - Given I am in t/samples/animals/csharp +ok 209 - And analizo must report that file cat.h not declares module Dog # -ok 205 - When I run "analizo files-graph ." +# Scenario C++, running against current directory +ok 210 - Given I am in t/samples/animals/cpp # -ok 206 - Then analizo must report that "Mammal" depends on "Animal" +ok 211 - When I run "analizo metrics ." # -# Feature loading command line options from .analizo -# As a analizo user I want to store command line options in a file called .analizo inside my project So that I don't need to alway pass all those options on the command line -# Scenario analizo metrics -ok 207 - Given I copy t/samples/mixed into a temporary directory +ok 212 - Then analizo must report that file animal.h declares module Animal # -ok 208 - And I create a file called .analizo with the following content -# """metrics: --language java""" -ok 209 - When I run "analizo metrics ." +ok 213 - And analizo must report that file cat.cc declares module Cat # -ok 210 - Then the output must not match "native_backend.c" +ok 214 - And analizo must report that file cat.h declares module Cat # -ok 211 - And the output must match "UI.java" +# Scenario Java +ok 215 - When I run "analizo metrics t/samples/animals/java" # -ok 212 - And the exit status must be 0 +ok 216 - Then analizo must report that file Animal.java declares module Animal # -# Scenario all others -ok 213 - Given I change to an empty temporary directory +# Scenario C +ok 217 - Given I am in t/samples/hello_world/c # -ok 214 - And I create a file called .analizo with the following content -# """: --help""" -ok 215 - When I run "analizo graph" +ok 218 - When I run "analizo metrics ." # -ok 216 - Then the output must match "analizo graph is part of the analizo suite." +ok 219 - Then analizo must report that module hello_world has _filename = [hello_world.c,hello_world.h] # -# Scenario all others -ok 217 - Given I change to an empty temporary directory +ok 220 - And analizo must report that file hello_world.c declares module hello_world # -ok 218 - And I create a file called .analizo with the following content -# """: --help""" -ok 219 - When I run "analizo metrics" +ok 221 - And analizo must report that file hello_world.h declares module hello_world # -ok 220 - Then the output must match "analizo metrics is part of the analizo suite." +# Scenario CSharp hello_world +ok 222 - Given I am in t/samples/hello_world/csharp # -# Scenario all others -ok 221 - Given I change to an empty temporary directory +ok 223 - When I run "analizo metrics ." # -ok 222 - And I create a file called .analizo with the following content -# """: --help""" -ok 223 - When I run "analizo metrics-batch" +ok 224 - Then analizo must report that module HelloWorld has _filename = [HelloWorld.cs] # -ok 224 - Then the output must match "analizo metrics-batch is part of the analizo suite." +# Scenario CSharp polygons +ok 225 - Given I am in t/samples/polygons/csharp # -# Scenario all others -ok 225 - Given I change to an empty temporary directory +ok 226 - When I run "analizo metrics ." # -ok 226 - And I create a file called .analizo with the following content -# """: --help""" -ok 227 - When I run "analizo metrics-history" +ok 227 - Then analizo must report that file Polygon.cs declares module Polygon # -ok 228 - Then the output must match "analizo metrics-history is part of the analizo suite." +ok 228 - And analizo must report that file Rect.cs declares module Rect # -# Scenario all others -ok 229 - Given I change to an empty temporary directory +ok 229 - And analizo must report that file Triangle.cs declares module Triangle # -ok 230 - And I create a file called .analizo with the following content -# """: --help""" -ok 231 - When I run "analizo tree-evolution" +# Scenario Java Generics WildCard sample +ok 230 - Given I am in t/samples/wildcard # -ok 232 - Then the output must match "analizo tree-evolution is part of the analizo suite." +ok 231 - When I run "analizo metrics ." # -# Scenario all others -ok 233 - Given I change to an empty temporary directory +ok 232 - Then analizo must report that file WildcardClass.java declares module WildcardClass # -ok 234 - And I create a file called .analizo with the following content -# """: --help""" -ok 235 - When I run "analizo files-graph" +ok 233 - And analizo must report that file GenericClass.java declares module GenericClass # -ok 236 - Then the output must match "analizo files-graph is part of the analizo suite." +# Scenario Java Enumeration sample +ok 234 - Given I am in t/samples/enumeration # -# Scenario all others -ok 237 - Given I change to an empty temporary directory +ok 235 - When I run "analizo metrics ." # -ok 238 - And I create a file called .analizo with the following content -# """: --help""" -ok 239 - When I run "analizo help" +ok 236 - Then analizo must report that file Main.java declares module Main::MyEnumeration # -ok 240 - Then the output must match "analizo help is part of the analizo suite." +ok 237 - And analizo must report that file Enumeration.java declares module Enumeration # # Feature c code with void argument # As a software engineering reasearcher I want to know the arguments of each function on a project So that I can run analizo metrics calculate number of parameters # Scenario calculate anpn on function with void argument -ok 241 - Given I am in t/samples/void/ +ok 238 - Given I am in t/samples/void/ # -ok 242 - When I run "analizo metrics ." +ok 239 - When I run "analizo metrics ." # -ok 243 - Then analizo must report that module main has anpm = 0 +ok 240 - Then analizo must report that module main has anpm = 0 # -# Feature doxyparse extractor external tool -# As a Analizo developer I want to guarantee that doxyparse deal with any source code To provide reliability for Analizo users -# Scenario don't die parsing MCLinker.cpp from android 5.1.1 -ok 244 - Given I am in t/samples/android-framework/android-5.1.1_r38 +# Feature analizo metrics-history +# As a software engineering researcher I want to analyse the entire history of a project To understand its development process +# Scenario listing merge commits with code changes that should be analyzed +ok 241 - When I explode t/samples/evolution.tar.gz # -ok 245 - When I run "analizo metrics ." +ok 242 - And I run "analizo metrics-history --list ." # -ok 246 - Then the exit status must be 0 +ok 243 - Then the output must match "0a06a6fcc2e7b4fe56d134e89d74ad028bb122ed" # -# Scenario don't duplicate YAML keys parsing AudioTrackShared.cpp from android 5.1.1 -ok 247 - Given I am in t/samples/android-framework/android-5.1.1_r38 +ok 244 - And the output must match "eb67c27055293e835049b58d7d73ce3664d3f90e" # -ok 248 - When I run "analizo metrics ." +ok 245 - And the output must match "aa2d0fcb7879485d5ff1cd189743f91f04bea8ce" # -ok 249 - Then analizo must not emit a warning matching "YAML_LOAD_WARN_DUPLICATE_KEY" +ok 246 - And the output must match "e8faf88f0e20a193d700b6c68eeb31897dd85e53" # -# Scenario don't abort parsing mlpack 3.0.0 -ok 250 - Given I am in t/samples/mlpack-3.0.0 +ok 247 - And the output must match "d7f52e74dc3d8f57640e83d41c5e9f8fcf621c00" # -ok 251 - When I run "analizo metrics ." +ok 248 - And the output must match "0d3c023120ad4e9f519a03fff275d048c52671ad" # -ok 252 - Then analizo must not emit a warning matching "Aborted" +# Scenario non-code commits should not be analyzed +ok 249 - When I explode t/samples/evolution.tar.gz # -ok 253 - And the exit status must be 0 +ok 250 - And I run "analizo metrics-history --list ." # -# Scenario don't die parsing kdelibs warning about unknown escape character -ok 254 - Given I am in t/samples/kdelibs +ok 251 - Then the output must not match "ba62278e976944c0334103aa0044535169e1a51e" # -ok 255 - When I run "analizo metrics ." +# Scenario merge commits without code change should not be analyzed +ok 252 - When I explode t/samples/evolution.tar.gz # -ok 256 - Then analizo must not emit a warning matching "Error" +ok 253 - And I run "analizo metrics-history --list ." # -ok 257 - And the exit status must be 0 +ok 254 - Then the output must not match "0fdaaa7dcc8073332a957024fafc8c98f165e725" # -# Scenario don't die parsing mod_suexec.h from http 2.4.38 -ok 258 - Given I am in t/samples/httpd-2.4.38 +# Scenario actually processing merge commits +ok 255 - When I explode t/samples/evolution.tar.gz # -ok 259 - When I run "analizo metrics ." +ok 256 - And I run "analizo metrics-history -o metrics.csv . && cat metrics.csv" # -ok 260 - Then analizo must not emit a warning matching "Not a HASH reference" +ok 257 - Then the output must match "^id,previous_commit_id,author_date,author_name,author_email,.*,sc_mean" # -ok 261 - And the exit status must be 0 +ok 258 - And the output must match "0a06a6fcc2e7b4fe56d134e89d74ad028bb122ed,eb67c27055293e835049b58d7d73ce3664d3f90e" # -# Scenario allow dot on module filename -ok 262 - Given I am in t/samples/sample_basic/c +ok 259 - And the output must match "eb67c27055293e835049b58d7d73ce3664d3f90e,," # -ok 263 - When I run "analizo metrics ." +ok 260 - And the output must match "aa2d0fcb7879485d5ff1cd189743f91f04bea8ce,d7f52e74dc3d8f57640e83d41c5e9f8fcf621c00" # -ok 264 - Then analizo must report that file module1.c declares module module1 +ok 261 - And the output must match "e8faf88f0e20a193d700b6c68eeb31897dd85e53,d7f52e74dc3d8f57640e83d41c5e9f8fcf621c00" # -# Feature tree evolution -# As a software engineering reasearcher I want to know what directories existed during the project lifetime So that I can analyze only the production code (and not tests etc) -# Scenario sample git repository -ok 265 - When I explode t/samples/tree-evolution.tar.gz +ok 262 - And the output must match "d7f52e74dc3d8f57640e83d41c5e9f8fcf621c00,0d3c023120ad4e9f519a03fff275d048c52671ad" # -ok 266 - And I run "analizo tree-evolution" +# Scenario actually processing initial commit and first commit after a non-relevant merge +ok 263 - When I explode t/samples/evolution.tar.gz # -ok 267 - Then the output lines must match "\# 073290fbad0254793bd3ecfb97654c04368d0039\\nsrc\\n\#" +ok 264 - And I run "analizo metrics-history -o metrics.csv . && cat metrics.csv" # -ok 268 - Then the output lines must match "\# 85f7db08f7b7b0b62e3c0023b2743d529b0d5b4b\\nsrc\\nsrc/input\\n\#" +ok 265 - Then the output must match "0d3c023120ad4e9f519a03fff275d048c52671ad,," # -ok 269 - Then the output lines must match "\# f41cf7d0351e812285efd60c6d957c330b1f61a1\\nsrc\\nsrc/input\\nsrc/output" +ok 266 - And the output must match "8183eafad3a0f3eff6e8869f1bdbfd255e86825a,0a06a6fcc2e7b4fe56d134e89d74ad028bb122ed" # -# Feature analizo metrics-history -# As a software engineering researcher I want to analyse the entire history of a project To understand its development process -# Scenario listing merge commits with code changes that should be analyzed -ok 270 - When I explode t/samples/evolution.tar.gz +# Scenario support for parallel processing +ok 267 - Given I copy t/samples/evolution.tar.gz into a temporary directory # -ok 271 - And I run "analizo metrics-history --list ." +ok 268 - When I run "tar xzf evolution.tar.gz" # -ok 272 - Then the output must match "0a06a6fcc2e7b4fe56d134e89d74ad028bb122ed" +ok 269 - And I run "cd evolution && analizo metrics-history -o ../sequential.csv" # -ok 273 - And the output must match "eb67c27055293e835049b58d7d73ce3664d3f90e" +ok 270 - And I run "cd evolution && analizo metrics-history -p 2 -o ../parallel.csv" # -ok 274 - And the output must match "aa2d0fcb7879485d5ff1cd189743f91f04bea8ce" +ok 271 - Then the exit status must be 0 # -ok 275 - And the output must match "e8faf88f0e20a193d700b6c68eeb31897dd85e53" +ok 272 - When I run "sort sequential.csv > sequential-sorted.csv" # -ok 276 - And the output must match "d7f52e74dc3d8f57640e83d41c5e9f8fcf621c00" +ok 273 - And I run "sort parallel.csv > parallel-sorted.csv" # -ok 277 - And the output must match "0d3c023120ad4e9f519a03fff275d048c52671ad" +ok 274 - And I run "diff -u sequential-sorted.csv parallel-sorted.csv" # -# Scenario non-code commits should not be analyzed -ok 278 - When I explode t/samples/evolution.tar.gz +ok 275 - Then the output must not match "---" # -ok 279 - And I run "analizo metrics-history --list ." +ok 276 - And the exit status must be 0 # -ok 280 - Then the output must not match "ba62278e976944c0334103aa0044535169e1a51e" +# Scenario parsing git log format containing renamed files among status of changed files +ok 277 - Given I copy t/samples/evolution.tar.gz into a temporary directory # -# Scenario merge commits without code change should not be analyzed -ok 281 - When I explode t/samples/evolution.tar.gz +ok 278 - When I run "tar xzf evolution.tar.gz" # -ok 282 - And I run "analizo metrics-history --list ." +ok 279 - And I run "cd evolution && git checkout doc && analizo metrics-history ." # -ok 283 - Then the output must not match "0fdaaa7dcc8073332a957024fafc8c98f165e725" +ok 280 - Then the exit status must be 0 # -# Scenario actually processing merge commits -ok 284 - When I explode t/samples/evolution.tar.gz +# Scenario language filters +ok 281 - Given I copy t/samples/mixed into a temporary directory # -ok 285 - And I run "analizo metrics-history -o metrics.csv . && cat metrics.csv" +ok 282 - When I run "(cd mixed && git init && git add * && git commit -m 'initial commit')" # -ok 286 - Then the output must match "^id,previous_commit_id,author_date,author_name,author_email,.*,sc_mean" +ok 283 - And I run "analizo metrics-history --language java mixed" # -ok 287 - And the output must match "0a06a6fcc2e7b4fe56d134e89d74ad028bb122ed,eb67c27055293e835049b58d7d73ce3664d3f90e" +ok 284 - Then the output must not match "native_backend.c" # -ok 288 - And the output must match "eb67c27055293e835049b58d7d73ce3664d3f90e,," +# Feature give manpage on --help +# As a user I want to read the manpage when passing --help command line option In order to get instructions on how to use the tools +# Scenario display manpage for `analizo graph` +ok 285 - When I run "analizo graph --help" # -ok 289 - And the output must match "aa2d0fcb7879485d5ff1cd189743f91f04bea8ce,d7f52e74dc3d8f57640e83d41c5e9f8fcf621c00" +ok 286 - Then the output must match "[NAME|N^HNA^HAM^HME^HE]\s+analizo-graph" # -ok 290 - And the output must match "e8faf88f0e20a193d700b6c68eeb31897dd85e53,d7f52e74dc3d8f57640e83d41c5e9f8fcf621c00" +ok 287 - Then the output must match "[USAGE|U^HUS^HSA^HAG^HGE^HE]\s+analizo graph \[OPTIONS\]" # -ok 291 - And the output must match "d7f52e74dc3d8f57640e83d41c5e9f8fcf621c00,0d3c023120ad4e9f519a03fff275d048c52671ad" +# Scenario display manpage for `analizo metrics` +ok 288 - When I run "analizo metrics --help" # -# Scenario actually processing initial commit and first commit after a non-relevant merge -ok 292 - When I explode t/samples/evolution.tar.gz +ok 289 - Then the output must match "[NAME|N^HNA^HAM^HME^HE]\s+analizo-metrics" # -ok 293 - And I run "analizo metrics-history -o metrics.csv . && cat metrics.csv" +ok 290 - Then the output must match "[USAGE|U^HUS^HSA^HAG^HGE^HE]\s+analizo metrics \[OPTIONS\]" # -ok 294 - Then the output must match "0d3c023120ad4e9f519a03fff275d048c52671ad,," +# Scenario display manpage for `analizo metrics-batch` +ok 291 - When I run "analizo metrics-batch --help" # -ok 295 - And the output must match "8183eafad3a0f3eff6e8869f1bdbfd255e86825a,0a06a6fcc2e7b4fe56d134e89d74ad028bb122ed" +ok 292 - Then the output must match "[NAME|N^HNA^HAM^HME^HE]\s+analizo-metrics-batch" # -# Scenario support for parallel processing -ok 296 - Given I copy t/samples/evolution.tar.gz into a temporary directory +ok 293 - Then the output must match "[USAGE|U^HUS^HSA^HAG^HGE^HE]\s+analizo metrics-batch \[OPTIONS\]" # -ok 297 - When I run "tar xzf evolution.tar.gz" +# Scenario display manpage for `analizo metrics-history` +ok 294 - When I run "analizo metrics-history --help" # -ok 298 - And I run "cd evolution && analizo metrics-history -o ../sequential.csv" +ok 295 - Then the output must match "[NAME|N^HNA^HAM^HME^HE]\s+analizo-metrics-history" # -ok 299 - And I run "cd evolution && analizo metrics-history -p 2 -o ../parallel.csv" +ok 296 - Then the output must match "[USAGE|U^HUS^HSA^HAG^HGE^HE]\s+analizo metrics-history \[OPTIONS\]" # -ok 300 - Then the exit status must be 0 +# Scenario display manpage for `analizo tree-evolution` +ok 297 - When I run "analizo tree-evolution --help" # -ok 301 - When I run "sort sequential.csv > sequential-sorted.csv" +ok 298 - Then the output must match "[NAME|N^HNA^HAM^HME^HE]\s+analizo-tree-evolution" # -ok 302 - And I run "sort parallel.csv > parallel-sorted.csv" +ok 299 - Then the output must match "[USAGE|U^HUS^HSA^HAG^HGE^HE]\s+analizo tree-evolution \[OPTIONS\]" # -ok 303 - And I run "diff -u sequential-sorted.csv parallel-sorted.csv" +# Scenario display manpage for `analizo files-graph` +ok 300 - When I run "analizo files-graph --help" # -ok 304 - Then the output must not match "---" +ok 301 - Then the output must match "[NAME|N^HNA^HAM^HME^HE]\s+analizo-files-graph" # -ok 305 - And the exit status must be 0 +ok 302 - Then the output must match "[USAGE|U^HUS^HSA^HAG^HGE^HE]\s+analizo files-graph \[OPTIONS\]" # -# Scenario parsing git log format containing renamed files among status of changed files -ok 306 - Given I copy t/samples/evolution.tar.gz into a temporary directory +# Feature analizo wrapper script +# Scenario invoking a tool +ok 303 - When I run "analizo metrics lib t" # -ok 307 - When I run "tar xzf evolution.tar.gz" +ok 304 - Then analizo must emit a warning matching "Usage:" # -ok 308 - And I run "cd evolution && git checkout doc && analizo metrics-history ." +ok 305 - And analizo must emit a warning matching "analizo.metrics" # -ok 309 - Then the exit status must be 0 +ok 306 - And the exit status must not be 0 # -# Scenario language filters -ok 310 - Given I copy t/samples/mixed into a temporary directory +# Scenario must not pass --version ahead +ok 307 - When I run "analizo metrics --version" # -ok 311 - When I run "(cd mixed && git init && git add * && git commit -m 'initial commit')" +ok 308 - Then analizo must emit a warning matching "Invalid option: --version" # -ok 312 - And I run "analizo metrics-history --language java mixed" +ok 309 - And the exit status must not be 0 # -ok 313 - Then the output must not match "native_backend.c" +# Scenario display help +ok 310 - When I run "analizo --help" # -# Feature mapping modules to filenames -# As a software engineering resesearcher I want to know in which file each module is declared So that I can compare that with data from the VCS -# Scenario C++, runing against some directory -ok 314 - When I run "analizo metrics t/samples/animals/cpp" +ok 311 - Then the output must match "[NAME|N^HNA^HAM^HME^HE]\s+analizo\s" # -ok 315 - Then analizo must report that file animal.h declares module Animal +ok 312 - And the output must match "[USAGE|U^HUS^HSA^HAG^HGE^HE]\s+analizo\s" # -ok 316 - And analizo must report that file cat.cc declares module Cat +ok 313 - And the exit status must be 0 # -ok 317 - And analizo must report that file cat.h declares module Cat +# Scenario display version +ok 314 - When I run "analizo --version" # -ok 318 - And analizo must report that file cat.cc not declares module Dog +ok 315 - Then the output must match "^analizo version [0-9]+.[0-9]+.[0-9]+" # -ok 319 - And analizo must report that file cat.h not declares module Dog +ok 316 - And the exit status must be 0 # -# Scenario C++, running against current directory -ok 320 - Given I am in t/samples/animals/cpp +# Scenario invalid option +ok 317 - When I run "analizo --invalid-option" # -ok 321 - When I run "analizo metrics ." +ok 318 - Then the output must match "Unrecognized command" # -ok 322 - Then analizo must report that file animal.h declares module Animal +ok 319 - And the exit status must not be 0 # -ok 323 - And analizo must report that file cat.cc declares module Cat +# Feature tree evolution +# As a software engineering reasearcher I want to know what directories existed during the project lifetime So that I can analyze only the production code (and not tests etc) +# Scenario sample git repository +ok 320 - When I explode t/samples/tree-evolution.tar.gz # -ok 324 - And analizo must report that file cat.h declares module Cat +ok 321 - And I run "analizo tree-evolution" # -# Scenario Java -ok 325 - When I run "analizo metrics t/samples/animals/java" +ok 322 - Then the output lines must match "\# 073290fbad0254793bd3ecfb97654c04368d0039\\nsrc\\n\#" # -ok 326 - Then analizo must report that file Animal.java declares module Animal +ok 323 - Then the output lines must match "\# 85f7db08f7b7b0b62e3c0023b2743d529b0d5b4b\\nsrc\\nsrc/input\\n\#" # -# Scenario C -ok 327 - Given I am in t/samples/hello_world/c +ok 324 - Then the output lines must match "\# f41cf7d0351e812285efd60c6d957c330b1f61a1\\nsrc\\nsrc/input\\nsrc/output" # -ok 328 - When I run "analizo metrics ." +# Feature storing VCS data in a database +# As a software engineering researcher I want to store data about the changes in a project So that I can analyze the development process +# Scenario basics +ok 325 - When I explode t/samples/evolution.tar.gz # -ok 329 - Then analizo must report that module hello_world has _filename = [hello_world.c,hello_world.h] +ok 326 - And I run "analizo metrics-history -f db -o data.db" # -ok 330 - And analizo must report that file hello_world.c declares module hello_world +ok 327 - Then the exit status must be 0 # -ok 331 - And analizo must report that file hello_world.h declares module hello_world +ok 328 - When I run "select * from modules" on database "data.db" # -# Scenario CSharp hello_world -ok 332 - Given I am in t/samples/hello_world/csharp +ok 329 - Then the output must match "Input" # -ok 333 - When I run "analizo metrics ." +ok 330 - And the output must match "Output" # -ok 334 - Then analizo must report that module HelloWorld has _filename = [HelloWorld.cs] +ok 331 - And the output must match "prog" # -# Scenario CSharp polygons -ok 335 - Given I am in t/samples/polygons/csharp +# Feature metrics batch +# As a software engineering researcher I want to analyze several different projects So I can compare their metrics +# Scenario "hello, world" +ok 332 - Given I am in t/samples/hello_world/ # -ok 336 - When I run "analizo metrics ." +ok 333 - When I run "analizo metrics-batch" # -ok 337 - Then analizo must report that file Polygon.cs declares module Polygon +ok 334 - Then the output must match "I: Processed c." # -ok 338 - And analizo must report that file Rect.cs declares module Rect +ok 335 - And the output must match "I: Processed cpp." # -ok 339 - And analizo must report that file Triangle.cs declares module Triangle +ok 336 - And the output must match "I: Processed java." # -# Scenario Java Generics WildCard sample -ok 340 - Given I am in t/samples/wildcard +# Scenario summarizing +ok 337 - Given I am in t/samples/hello_world/ # -ok 341 - When I run "analizo metrics ." +ok 338 - When I run "analizo metrics-batch --quiet -o data.csv && cat data.csv && rm -f *.csv" # -ok 342 - Then analizo must report that file WildcardClass.java declares module WildcardClass +ok 339 - Then the output must match "^id," # -ok 343 - And analizo must report that file GenericClass.java declares module GenericClass +ok 340 - And the output must not match ",---," # -# Scenario Java Enumeration sample -ok 344 - Given I am in t/samples/enumeration +ok 341 - And the output must match "c," # -ok 345 - When I run "analizo metrics ." +ok 342 - And the output must match "cpp," # -ok 346 - Then analizo must report that file Main.java declares module Main::MyEnumeration +ok 343 - And the output must match "java," # -ok 347 - And analizo must report that file Enumeration.java declares module Enumeration +ok 344 - And the output must not match "I: Processed" # -# Feature analizo wrapper script -# Scenario invoking a tool -ok 348 - When I run "analizo metrics lib t" +# Scenario support for parallel processing +ok 345 - Given I copy t/samples/hello_world/* into a temporary directory # -ok 349 - Then analizo must emit a warning matching "Usage:" +ok 346 - When I run "analizo metrics-batch -q -o sequential.csv" # -ok 350 - And analizo must emit a warning matching "analizo.metrics" +ok 347 - And I run "analizo metrics-batch -q -o parallel.csv -p 2" # -ok 351 - And the exit status must not be 0 +ok 348 - And I run "sort sequential.csv > sequential-sorted.csv" # -# Scenario must not pass --version ahead -ok 352 - When I run "analizo metrics --version" +ok 349 - And I run "sort parallel.csv > parallel-sorted.csv" # -ok 353 - Then analizo must emit a warning matching "Invalid option: --version" +ok 350 - And I run "diff -u sequential-sorted.csv parallel-sorted.csv" # -ok 354 - And the exit status must not be 0 +ok 351 - Then the output must not match "---" # -# Scenario display help -ok 355 - When I run "analizo --help" +ok 352 - Then the exit status must be 0 # -ok 356 - Then the output must match "[NAME|N^HNA^HAM^HME^HE]\s+analizo\s" +# Scenario passing two input directories as argument +ok 353 - Given I copy t/samples/hello_world/* into a temporary directory # -ok 357 - And the output must match "[USAGE|U^HUS^HSA^HAG^HGE^HE]\s+analizo\s" +ok 354 - When I run "analizo metrics-batch --quiet -o data.csv cpp java" # -ok 358 - And the exit status must be 0 +ok 355 - Then the exit status must be 0 # -# Scenario display version -ok 359 - When I run "analizo --version" +ok 356 - And the file "c-details.csv" should not exist # -ok 360 - Then the output must match "^analizo version [0-9]+.[0-9]+.[0-9]+" +ok 357 - And the file "cpp-details.csv" should exist # -ok 361 - And the exit status must be 0 +ok 358 - And the file "java-details.csv" should exist # -# Scenario invalid option -ok 362 - When I run "analizo --invalid-option" +# Scenario passing one input directory as argument +ok 359 - Given I copy t/samples/hello_world/* into a temporary directory # -ok 363 - Then the output must match "Unrecognized command" +ok 360 - When I run "analizo metrics-batch --quiet -o data.csv cpp" # -ok 364 - And the exit status must not be 0 +ok 361 - Then the exit status must be 0 # -# Feature displaying version -# Scenario running without any arguments -ok 365 - When I run "analizo graph" +ok 362 - And the file "c-details.csv" should not exist # -ok 366 - Then analizo must emit a warning matching "Usage:" +ok 363 - And the file "cpp-details.csv" should exist # -ok 367 - And the exit status must not be 0 +ok 364 - And the file "java-details.csv" should not exist # -# Feature clustering subroutines in the same module together -# Scenario clustering dependencies -ok 368 - Given I am in t/samples/sample_basic/c/ +# Feature output file for graph tool +# Scenario passing output file in the command line +ok 365 - Given I am in . # -ok 369 - When I run "analizo graph --cluster ." +ok 366 - When I run "analizo graph --output output.dot.tmp t/samples/sample_basic/c/" # -ok 370 - Then analizo must report that "module1::main()" is part of "module1" +ok 367 - Then the contents of "output.dot.tmp" must match "module1" # -ok 371 - Then analizo must report that "module2::say_hello()" is part of "module2" +ok 368 - And the exit status must be 0 # -ok 372 - Then analizo must report that "module2::say_bye()" is part of "module2" +# Scenario passing output file in an unexisting directory +ok 369 - Given I am in . # -ok 373 - Then analizo must report that "module3::variable" is part of "module3" +ok 370 - When I run "analizo graph --output /this/directory/must/not/exists/output.dot t/samples/sample_basic/c/" # -ok 374 - Then analizo must report that "module3::callback()" is part of "module3" +ok 371 - Then analizo must emit a warning matching "No such file or directory" # -# Feature plain analizo graph run -# Scenario simply running analizo -ok 375 - Given I am in t/samples/sample_basic/c/ +ok 372 - And the exit status must not be 0 # -ok 376 - When I run "analizo graph ." +# Scenario passing output file without permission to write +ok 373 - Given I am in . # -ok 377 - Then analizo must report that "module1::main()" depends on "module3::variable" +ok 374 - When I run "touch output.tmp" # -ok 378 - Then analizo must report that "module1::main()" depends on "module3::callback()" +ok 375 - And I run "chmod 000 output.tmp" # -ok 379 - Then analizo must report that "module1::main()" depends on "module2::say_bye()" +ok 376 - And I run "analizo graph --output output.tmp t/samples/sample_basic/c/" # -ok 380 - Then analizo must report that "module1::main()" depends on "module2::say_hello()" +ok 377 - Then the exit status must not be 0 # -ok 381 - And the exit status must be 0 +ok 378 - And analizo must emit a warning matching "Permission denied" # -# Feature functions calls -# Scenario detect function calls among classes -ok 382 - Given I am in t/samples/animals/cpp +# Feature displaying version +# Scenario running without any arguments +ok 379 - When I run "analizo graph" # -ok 383 - When I run "analizo graph ." +ok 380 - Then analizo must emit a warning matching "Usage:" # -ok 384 - Then analizo must report that "Cat::Cat(char *)" depends on "Cat::_name" +ok 381 - And the exit status must not be 0 # -ok 385 - And analizo must not report that "Cat::Cat(char *)" depends on "Cat::name()" +# Feature input files for graph tool +# Scenario passing specific files in the command line +ok 382 - Given I am in t/samples/sample_basic/c # -ok 386 - And the exit status must be 0 +ok 383 - When I run "analizo graph module1.c module2.c" # -# Feature output file for graph tool -# Scenario passing output file in the command line -ok 387 - Given I am in . +ok 384 - Then the output must match "module1" # -ok 388 - When I run "analizo graph --output output.dot.tmp t/samples/sample_basic/c/" +ok 385 - And the output must match "module2" # -ok 389 - Then the contents of "output.dot.tmp" must match "module1" +ok 386 - And the output must not match "module3" # -ok 390 - And the exit status must be 0 +# Scenario passing unexisting file +ok 387 - Given I am in t/samples/sample_basic/c # -# Scenario passing output file in an unexisting directory -ok 391 - Given I am in . +ok 388 - When I run "analizo graph unexisting-file.c" # -ok 392 - When I run "analizo graph --output /this/directory/must/not/exists/output.dot t/samples/sample_basic/c/" +ok 389 - Then analizo must emit a warning matching "is not readable" # -ok 393 - Then analizo must emit a warning matching "No such file or directory" +# Feature functions calls +# Scenario detect function calls among classes +ok 390 - Given I am in t/samples/animals/cpp # -ok 394 - And the exit status must not be 0 +ok 391 - When I run "analizo graph ." # -# Scenario passing output file without permission to write -ok 395 - Given I am in . +ok 392 - Then analizo must report that "Cat::Cat(char *)" depends on "Cat::_name" # -ok 396 - When I run "touch output.tmp" +ok 393 - And analizo must not report that "Cat::Cat(char *)" depends on "Cat::name()" # -ok 397 - And I run "chmod 000 output.tmp" +ok 394 - And the exit status must be 0 # -ok 398 - And I run "analizo graph --output output.tmp t/samples/sample_basic/c/" +# Feature group by modules +# Scenario sample project +ok 395 - Given I am in t/samples/sample_basic/c/ # -ok 399 - Then the exit status must not be 0 +ok 396 - When I run "analizo graph --modules ." # -ok 400 - And analizo must emit a warning matching "Permission denied" +ok 397 - Then analizo must report that "module1" depends on "module2" # -# Feature input files for graph tool -# Scenario passing specific files in the command line -ok 401 - Given I am in t/samples/sample_basic/c +ok 398 - Then analizo must report that "module1" depends on "module3" # -ok 402 - When I run "analizo graph module1.c module2.c" +# Feature clustering subroutines in the same module together +# Scenario clustering dependencies +ok 399 - Given I am in t/samples/sample_basic/c/ # -ok 403 - Then the output must match "module1" +ok 400 - When I run "analizo graph --cluster ." # -ok 404 - And the output must match "module2" +ok 401 - Then analizo must report that "module1::main()" is part of "module1" # -ok 405 - And the output must not match "module3" +ok 402 - Then analizo must report that "module2::say_hello()" is part of "module2" # -# Scenario passing unexisting file -ok 406 - Given I am in t/samples/sample_basic/c +ok 403 - Then analizo must report that "module2::say_bye()" is part of "module2" # -ok 407 - When I run "analizo graph unexisting-file.c" +ok 404 - Then analizo must report that "module3::variable" is part of "module3" # -ok 408 - Then analizo must emit a warning matching "is not readable" +ok 405 - Then analizo must report that "module3::callback()" is part of "module3" # -# Feature group by modules -# Scenario sample project -ok 409 - Given I am in t/samples/sample_basic/c/ +# Feature plain analizo graph run +# Scenario simply running analizo +ok 406 - Given I am in t/samples/sample_basic/c/ +# +ok 407 - When I run "analizo graph ." # -ok 410 - When I run "analizo graph --modules ." +ok 408 - Then analizo must report that "module1::main()" depends on "module3::variable" # -ok 411 - Then analizo must report that "module1" depends on "module2" +ok 409 - Then analizo must report that "module1::main()" depends on "module3::callback()" # -ok 412 - Then analizo must report that "module1" depends on "module3" +ok 410 - Then analizo must report that "module1::main()" depends on "module2::say_bye()" +# +ok 411 - Then analizo must report that "module1::main()" depends on "module2::say_hello()" +# +ok 412 - And the exit status must be 0 # # Feature omitting certain modules # Scenario omitting say_bye @@ -3853,1343 +3896,1343 @@ # ok 422 - Then the output must not match "module1::main()" # -# Feature number of abstract classes -# As a software developer I want analizo to report the number of modules with at least a defined method in my code So that I can evaluate it -# Scenario "Hello, world" project -ok 423 - Given I am in t/samples/hello_world/cpp +# Feature output only global metrics +# As a researcher I want to ouput only the global metrics So that I can evaluate several projects at once +# Scenario simple case +ok 423 - Given I am in t/samples/sample_basic/c/ # -ok 424 - When I run "analizo metrics ." +ok 424 - When I run "analizo metrics --global-only ." # -ok 425 - Then analizo must report that the project has total_modules_with_defined_attributes = 1 +ok 425 - Then the output must match "cbo_mean:" # -# Scenario "Hello, world" project -ok 426 - Given I am in t/samples/hello_world/java +ok 426 - And the output must not match "_module:" # -ok 427 - When I run "analizo metrics ." +# Scenario short version +ok 427 - Given I am in t/samples/sample_basic/c/ +# +ok 428 - When I run "analizo metrics -g ." +# +ok 429 - Then the output must match "cbo_mean:" # -ok 428 - Then analizo must report that the project has total_modules_with_defined_attributes = 1 +ok 430 - And the output must not match "_module:" # +# Feature number of abstract classes +# As a software developer I want analizo to report the number of abstract classes in my code So that I can evaluate it # Scenario "Hello, world" project -ok 429 - Given I am in t/samples/hello_world/csharp +ok 431 - Given I am in t/samples/hello_world/cpp # -ok 430 - When I run "analizo metrics ." +ok 432 - When I run "analizo metrics ." # -ok 431 - Then analizo must report that the project has total_modules_with_defined_attributes = 1 +ok 433 - Then analizo must report that the project has total_abstract_classes = 0 # -# Scenario "Animals" project -ok 432 - Given I am in t/samples/animals/cpp +# Scenario "Hello, world" project +ok 434 - Given I am in t/samples/hello_world/java # -ok 433 - When I run "analizo metrics ." +ok 435 - When I run "analizo metrics ." # -ok 434 - Then analizo must report that the project has total_modules_with_defined_attributes = 2 +ok 436 - Then analizo must report that the project has total_abstract_classes = 0 # -# Scenario "Animals" project -ok 435 - Given I am in t/samples/animals/java +# Scenario "Hello, world" project +ok 437 - Given I am in t/samples/hello_world/csharp # -ok 436 - When I run "analizo metrics ." +ok 438 - When I run "analizo metrics ." # -ok 437 - Then analizo must report that the project has total_modules_with_defined_attributes = 2 +ok 439 - Then analizo must report that the project has total_abstract_classes = 0 # # Scenario "Animals" project -ok 438 - Given I am in t/samples/animals/csharp +ok 440 - Given I am in t/samples/animals/cpp # -ok 439 - When I run "analizo metrics ." +ok 441 - When I run "analizo metrics ." # -ok 440 - Then analizo must report that the project has total_modules_with_defined_attributes = 2 +ok 442 - Then analizo must report that the project has total_abstract_classes = 2 # -# Feature total number of methods per abstract class -# As a software developer I want analizo to report the number of abstract classes in my code So that I can evaluate it -# Scenario "Hello, world" project -ok 441 - Given I am in t/samples/hello_world/cpp +# Scenario "Animals" project +ok 443 - Given I am in t/samples/animals/java # -ok 442 - When I run "analizo metrics ." +ok 444 - When I run "analizo metrics ." # -ok 443 - Then analizo must report that the project has total_methods_per_abstract_class = 0 +ok 445 - Then analizo must report that the project has total_abstract_classes = 2 # -# Scenario "Hello, world" project -ok 444 - Given I am in t/samples/hello_world/java +# Scenario "Animals" project +ok 446 - Given I am in t/samples/animals/csharp # -ok 445 - When I run "analizo metrics ." +ok 447 - When I run "analizo metrics ." # -ok 446 - Then analizo must report that the project has total_methods_per_abstract_class = 0 +ok 448 - Then analizo must report that the project has total_abstract_classes = 1 # -# Scenario "Hello, world" project -ok 447 - Given I am in t/samples/hello_world/csharp +# Scenario "Polygons" project +ok 449 - Given I am in t/samples/polygons/cpp # -ok 448 - When I run "analizo metrics ." +ok 450 - When I run "analizo metrics ." # -ok 449 - Then analizo must report that the project has total_methods_per_abstract_class = 0 +ok 451 - Then analizo must report that the project has total_abstract_classes = 2 # -# Scenario "Animals" project -ok 450 - Given I am in t/samples/animals/cpp -# -ok 451 - When I run "analizo metrics ." +# Scenario "Polygons" project +ok 452 - Given I am in t/samples/polygons/java # -ok 452 - Then analizo must report that the project has total_methods_per_abstract_class = 1 +ok 453 - When I run "analizo metrics ." # -# Scenario "Animals" project -ok 453 - Given I am in t/samples/animals/java +ok 454 - Then analizo must report that the project has total_abstract_classes = 2 # -ok 454 - When I run "analizo metrics ." +# Scenario "Polygons" project +ok 455 - Given I am in t/samples/polygons/csharp # -ok 455 - Then analizo must report that the project has total_methods_per_abstract_class = 1 +ok 456 - When I run "analizo metrics ." # -# Scenario "Animals" project -ok 456 - Given I am in t/samples/animals/csharp +ok 457 - Then analizo must report that the project has total_abstract_classes = 2 # -ok 457 - When I run "analizo metrics ." -# -ok 458 - Then analizo must report that the project has total_methods_per_abstract_class = 1 +# Scenario "AbstractClass" project +ok 458 - Given I am in t/samples/abstract_class/java # -# Scenario "Polygons" project -ok 459 - Given I am in t/samples/polygons/cpp +ok 459 - When I run "analizo metrics ." # -ok 460 - When I run "analizo metrics ." +ok 460 - Then analizo must report that the project has total_abstract_classes = 1 # -ok 461 - Then analizo must report that the project has total_methods_per_abstract_class = 2.5 +ok 461 - And analizo must report that the project has total_methods_per_abstract_class = 6 # -# Scenario "Polygons" project -ok 462 - Given I am in t/samples/polygons/java +# Scenario "AbstractClass" project +ok 462 - Given I am in t/samples/abstract_class/csharp # ok 463 - When I run "analizo metrics ." # -ok 464 - Then analizo must report that the project has total_methods_per_abstract_class = 2 +ok 464 - Then analizo must report that the project has total_abstract_classes = 1 # -# Scenario "Polygons" project -ok 465 - Given I am in t/samples/polygons/csharp +ok 465 - And analizo must report that the project has total_methods_per_abstract_class = 1 # -ok 466 - When I run "analizo metrics ." +# Feature average number of parameters metric +# As a software developer I want to calculate the average number of arguments per method metric So that I can evaluate my code +# Scenario number of parameters in the "Animals" project +ok 466 - Given I am in t/samples/animals/cpp # -ok 467 - Then analizo must report that the project has total_methods_per_abstract_class = 2 +ok 467 - When I run "analizo metrics ." # -# Feature number of methods -# As a software developer I want analizo to report the number of methods of each module So that I can evaluate it -# Scenario number of methods of the polygon java sample -ok 468 - Given I am in t/samples/polygons/cpp +ok 468 - Then analizo must report that module Dog has anpm = 0.5 # -ok 469 - When I run "analizo metrics ." +ok 469 - And analizo must report that module Cat has anpm = 0.5 # -ok 470 - Then analizo must report that module CPolygon has nom = 3 +ok 470 - And analizo must report that module main has anpm = 0 # -# Scenario number of methods of the polygon java sample -ok 471 - Given I am in t/samples/polygons/cpp +# Scenario number of parameters in the "Animals" project +ok 471 - Given I am in t/samples/animals/java # ok 472 - When I run "analizo metrics ." # -ok 473 - Then analizo must report that module CTetragon has nom = 2 +ok 473 - Then analizo must report that module Dog has anpm = 0.5 # -# Scenario number of methods of the polygon java sample -ok 474 - Given I am in t/samples/polygons/java +ok 474 - And analizo must report that module Cat has anpm = 0.5 # -ok 475 - When I run "analizo metrics ." +ok 475 - And analizo must report that module Main has anpm = 1 # -ok 476 - Then analizo must report that module Polygon has nom = 3 +# Scenario number of parameters in the "Animals" project +ok 476 - Given I am in t/samples/animals/csharp # -# Scenario number of methods of the polygon java sample -ok 477 - Given I am in t/samples/polygons/csharp +ok 477 - When I run "analizo metrics ." # -ok 478 - When I run "analizo metrics ." +ok 478 - Then analizo must report that module Dog has anpm = 0.5 # -ok 479 - Then analizo must report that module Polygon has nom = 2 +ok 479 - And analizo must report that module Cat has anpm = 0.5 # -# Scenario number of methods of the polygon java sample -ok 480 - Given I am in t/samples/polygons/csharp +ok 480 - And analizo must report that module main has anpm = 1 # -ok 481 - When I run "analizo metrics ." +# Feature afferent connections with deep inheritance +# As a software developer I want analizo to report the afferent connections of each module So that I can evaluate it +# Scenario afferent connections of the dog family java sample +ok 481 - Given I am in t/samples/deep_inheritance/java # -ok 482 - Then analizo must report that module Tetragon has nom = 2 +ok 482 - When I run "analizo metrics ." # -# Scenario number of methods of the polygon java sample -ok 483 - Given I am in t/samples/animals/cpp +ok 483 - Then analizo must report that module Dog has acc = 7 # -ok 484 - When I run "analizo metrics ." +# Scenario afferent connections of the dog family java sample +ok 484 - Given I am in t/samples/deep_inheritance/java # -ok 485 - Then analizo must report that module Animal has nom = 1 +ok 485 - When I run "analizo metrics ." # -# Scenario number of methods of the polygon java sample -ok 486 - Given I am in t/samples/animals/cpp +ok 486 - Then analizo must report that module DogFirstGreatGrandson has acc = 1 # -ok 487 - When I run "analizo metrics ." +# Scenario afferent connections of the dog family java sample +ok 487 - Given I am in t/samples/deep_inheritance/java # -ok 488 - Then analizo must report that module Cat has nom = 2 +ok 488 - When I run "analizo metrics ." # -# Scenario number of methods of the polygon java sample -ok 489 - Given I am in t/samples/animals/cpp +ok 489 - Then analizo must report that module DogFirstPuppy has acc = 4 # -ok 490 - When I run "analizo metrics ." +# Scenario afferent connections of the dog family java sample +ok 490 - Given I am in t/samples/deep_inheritance/java # -ok 491 - Then analizo must report that module Dog has nom = 2 +ok 491 - When I run "analizo metrics ." # -# Scenario number of methods of the polygon java sample -ok 492 - Given I am in t/samples/animals/java +ok 492 - Then analizo must report that module DogGrandson has acc = 3 # -ok 493 - When I run "analizo metrics ." +# Scenario afferent connections of the dog family java sample +ok 493 - Given I am in t/samples/deep_inheritance/java # -ok 494 - Then analizo must report that module Animal has nom = 1 +ok 494 - When I run "analizo metrics ." # -# Scenario number of methods of the polygon java sample -ok 495 - Given I am in t/samples/animals/java +ok 495 - Then analizo must report that module DogSecondGreatGrandson has acc = 0 # -ok 496 - When I run "analizo metrics ." +# Scenario afferent connections of the dog family java sample +ok 496 - Given I am in t/samples/deep_inheritance/java # -ok 497 - Then analizo must report that module Cat has nom = 2 +ok 497 - When I run "analizo metrics ." # -# Scenario number of methods of the polygon java sample -ok 498 - Given I am in t/samples/animals/java +ok 498 - Then analizo must report that module DogSecondPuppy has acc = 0 # -ok 499 - When I run "analizo metrics ." +# Scenario afferent connections of the dog family java sample +ok 499 - Given I am in t/samples/deep_inheritance/java # -ok 500 - Then analizo must report that module Dog has nom = 2 +ok 500 - When I run "analizo metrics ." # -# Scenario number of methods of the polygon java sample -ok 501 - Given I am in t/samples/animals/csharp +ok 501 - Then analizo must report that module DogSuperYoung has acc = 0 # -ok 502 - When I run "analizo metrics ." +# Scenario afferent connections of the dog family java sample +ok 502 - Given I am in t/samples/deep_inheritance/java # -ok 503 - Then analizo must report that module Animal has nom = 1 +ok 503 - When I run "analizo metrics ." # -# Scenario number of methods of the polygon java sample -ok 504 - Given I am in t/samples/animals/csharp +ok 504 - Then analizo must report that module Human has acc = 2 # -ok 505 - When I run "analizo metrics ." +# Scenario afferent connections of the dog family java sample +ok 505 - Given I am in t/samples/deep_inheritance/java # -ok 506 - Then analizo must report that module Cat has nom = 2 +ok 506 - When I run "analizo metrics ." # -# Scenario number of methods of the polygon java sample -ok 507 - Given I am in t/samples/animals/csharp +ok 507 - Then analizo must report that module ShopController has acc = 0 # -ok 508 - When I run "analizo metrics ." +# Scenario afferent connections of the dog family java sample +ok 508 - Given I am in t/samples/deep_inheritance/java # -ok 509 - Then analizo must report that module Dog has nom = 2 +ok 509 - When I run "analizo metrics ." # -# Scenario not computes macro on C code as method definition -ok 510 - Given I am in t/samples/macro +ok 510 - Then analizo must report that module VenderShop has acc = 1 # -ok 511 - When I run "analizo metrics ." +# Feature number of methods +# As a software developer I want analizo to report the number of methods of each module So that I can evaluate it +# Scenario number of methods of the polygon java sample +ok 511 - Given I am in t/samples/polygons/cpp # -ok 512 - Then analizo must report that module using_macro has nom = 1 +ok 512 - When I run "analizo metrics ." # -# Feature language filters -# As a software developer in a multi-language project I want to analyze only one programming language So that the results are as correct as possible -# Scenario filtering for C code -ok 513 - Given I am in t/samples/mixed +ok 513 - Then analizo must report that module CPolygon has nom = 3 # -ok 514 - When I run "analizo metrics --language c ." +# Scenario number of methods of the polygon java sample +ok 514 - Given I am in t/samples/polygons/cpp # -ok 515 - Then the output must match "native_backend" +ok 515 - When I run "analizo metrics ." # -ok 516 - And the output must not match "UI" +ok 516 - Then analizo must report that module CTetragon has nom = 2 # -ok 517 - And the output must not match "Backend" +# Scenario number of methods of the polygon java sample +ok 517 - Given I am in t/samples/polygons/java # -ok 518 - And the output must not match "CSharp_Backend" +ok 518 - When I run "analizo metrics ." # -# Scenario filtering for Java code -ok 519 - Given I am in t/samples/mixed +ok 519 - Then analizo must report that module Polygon has nom = 3 # -ok 520 - When I run "analizo metrics --language java ." +# Scenario number of methods of the polygon java sample +ok 520 - Given I am in t/samples/polygons/csharp # -ok 521 - Then the output must match "UI" +ok 521 - When I run "analizo metrics ." # -ok 522 - And the output must match "Backend" +ok 522 - Then analizo must report that module Polygon has nom = 2 # -ok 523 - And the output must not match "native_backend" +# Scenario number of methods of the polygon java sample +ok 523 - Given I am in t/samples/polygons/csharp # -ok 524 - And the output must not match "CSharp_Backend" +ok 524 - When I run "analizo metrics ." # -# Scenario filtering for CSharp code -ok 525 - Given I am in t/samples/mixed +ok 525 - Then analizo must report that module Tetragon has nom = 2 # -ok 526 - When I run "analizo metrics --language csharp ." +# Scenario number of methods of the polygon java sample +ok 526 - Given I am in t/samples/animals/cpp # -ok 527 - Then the output must match "CSharp_Backend" +ok 527 - When I run "analizo metrics ." # -ok 528 - And the output must not match "UI" +ok 528 - Then analizo must report that module Animal has nom = 1 # -ok 529 - And the output must not match "native_backend" +# Scenario number of methods of the polygon java sample +ok 529 - Given I am in t/samples/animals/cpp # -# Scenario listing languages -ok 530 - When I run "analizo metrics --language list" +ok 530 - When I run "analizo metrics ." # -ok 531 - Then analizo must present a list of languages +ok 531 - Then analizo must report that module Cat has nom = 2 # -# Feature number of attributes metric -# As a software developer I want to calculate the number of attributes per module metric So that I can evaluate my code -# Scenario number of attributes in the "Animals" project +# Scenario number of methods of the polygon java sample ok 532 - Given I am in t/samples/animals/cpp # ok 533 - When I run "analizo metrics ." # -ok 534 - Then analizo must report that module Dog has noa = 1 +ok 534 - Then analizo must report that module Dog has nom = 2 # -ok 535 - And analizo must report that module Cat has noa = 1 +# Scenario number of methods of the polygon java sample +ok 535 - Given I am in t/samples/animals/java # -ok 536 - And analizo must report that module main has noa = 0 +ok 536 - When I run "analizo metrics ." # -# Scenario number of attributes in the "Animals" project -ok 537 - Given I am in t/samples/animals/java +ok 537 - Then analizo must report that module Animal has nom = 1 # -ok 538 - When I run "analizo metrics ." +# Scenario number of methods of the polygon java sample +ok 538 - Given I am in t/samples/animals/java # -ok 539 - Then analizo must report that module Dog has noa = 1 +ok 539 - When I run "analizo metrics ." # -ok 540 - And analizo must report that module Cat has noa = 1 +ok 540 - Then analizo must report that module Cat has nom = 2 # -ok 541 - And analizo must report that module Main has noa = 0 +# Scenario number of methods of the polygon java sample +ok 541 - Given I am in t/samples/animals/java # -# Scenario number of attributes in the "Animals" project -ok 542 - Given I am in t/samples/animals/csharp +ok 542 - When I run "analizo metrics ." # -ok 543 - When I run "analizo metrics ." +ok 543 - Then analizo must report that module Dog has nom = 2 # -ok 544 - Then analizo must report that module Dog has noa = 1 +# Scenario number of methods of the polygon java sample +ok 544 - Given I am in t/samples/animals/csharp # -ok 545 - And analizo must report that module Cat has noa = 1 +ok 545 - When I run "analizo metrics ." # -ok 546 - And analizo must report that module main has noa = 0 +ok 546 - Then analizo must report that module Animal has nom = 1 # -# Feature average number of parameters metric -# As a software developer I want to calculate the average number of arguments per method metric So that I can evaluate my code -# Scenario number of parameters in the "Animals" project -ok 547 - Given I am in t/samples/animals/cpp +# Scenario number of methods of the polygon java sample +ok 547 - Given I am in t/samples/animals/csharp # ok 548 - When I run "analizo metrics ." # -ok 549 - Then analizo must report that module Dog has anpm = 0.5 +ok 549 - Then analizo must report that module Cat has nom = 2 # -ok 550 - And analizo must report that module Cat has anpm = 0.5 +# Scenario number of methods of the polygon java sample +ok 550 - Given I am in t/samples/animals/csharp # -ok 551 - And analizo must report that module main has anpm = 0 +ok 551 - When I run "analizo metrics ." # -# Scenario number of parameters in the "Animals" project -ok 552 - Given I am in t/samples/animals/java +ok 552 - Then analizo must report that module Dog has nom = 2 # -ok 553 - When I run "analizo metrics ." +# Scenario not computes macro on C code as method definition +ok 553 - Given I am in t/samples/macro # -ok 554 - Then analizo must report that module Dog has anpm = 0.5 +ok 554 - When I run "analizo metrics ." # -ok 555 - And analizo must report that module Cat has anpm = 0.5 +ok 555 - Then analizo must report that module using_macro has nom = 1 # -ok 556 - And analizo must report that module Main has anpm = 1 +# Feature number of abstract classes +# As a software developer I want analizo to report the number of modules with at least a defined method in my code So that I can evaluate it +# Scenario "Hello, world" project +ok 556 - Given I am in t/samples/hello_world/cpp # -# Scenario number of parameters in the "Animals" project -ok 557 - Given I am in t/samples/animals/csharp +ok 557 - When I run "analizo metrics ." # -ok 558 - When I run "analizo metrics ." +ok 558 - Then analizo must report that the project has total_modules_with_defined_methods = 2 # -ok 559 - Then analizo must report that module Dog has anpm = 0.5 +# Scenario "Hello, world" project +ok 559 - Given I am in t/samples/hello_world/java # -ok 560 - And analizo must report that module Cat has anpm = 0.5 +ok 560 - When I run "analizo metrics ." # -ok 561 - And analizo must report that module main has anpm = 1 +ok 561 - Then analizo must report that the project has total_modules_with_defined_methods = 2 # -# Feature number of abstract classes -# As a software developer I want analizo to report the number of modules with at least a defined method in my code So that I can evaluate it # Scenario "Hello, world" project -ok 562 - Given I am in t/samples/hello_world/cpp +ok 562 - Given I am in t/samples/hello_world/csharp # ok 563 - When I run "analizo metrics ." # ok 564 - Then analizo must report that the project has total_modules_with_defined_methods = 2 # -# Scenario "Hello, world" project -ok 565 - Given I am in t/samples/hello_world/java +# Scenario "Animals" project +ok 565 - Given I am in t/samples/animals/cpp # ok 566 - When I run "analizo metrics ." # -ok 567 - Then analizo must report that the project has total_modules_with_defined_methods = 2 +ok 567 - Then analizo must report that the project has total_modules_with_defined_methods = 5 # -# Scenario "Hello, world" project -ok 568 - Given I am in t/samples/hello_world/csharp +# Scenario "Animals" project +ok 568 - Given I am in t/samples/animals/java # ok 569 - When I run "analizo metrics ." # -ok 570 - Then analizo must report that the project has total_modules_with_defined_methods = 2 +ok 570 - Then analizo must report that the project has total_modules_with_defined_methods = 5 # # Scenario "Animals" project -ok 571 - Given I am in t/samples/animals/cpp +ok 571 - Given I am in t/samples/animals/csharp # ok 572 - When I run "analizo metrics ." # ok 573 - Then analizo must report that the project has total_modules_with_defined_methods = 5 # -# Scenario "Animals" project -ok 574 - Given I am in t/samples/animals/java +# Feature number of public methods metric +# As a software developer I want to calculate the number of public methods per module metric So that I can evaluate my code +# Scenario number of attributes in the "Animals" project +ok 574 - Given I am in t/samples/polygons/cpp # ok 575 - When I run "analizo metrics ." # -ok 576 - Then analizo must report that the project has total_modules_with_defined_methods = 5 +ok 576 - Then analizo must report that module CPolygon has npm = 2 # -# Scenario "Animals" project -ok 577 - Given I am in t/samples/animals/csharp +# Scenario number of attributes in the "Animals" project +ok 577 - Given I am in t/samples/polygons/cpp # ok 578 - When I run "analizo metrics ." # -ok 579 - Then analizo must report that the project has total_modules_with_defined_methods = 5 +ok 579 - Then analizo must report that module CTetragon has npm = 1 # -# Feature output statistics values of metrics -# As a researcher I want to ouput statistics values of metrics So that I can evaluate a project at once -# Scenario "Hello, world" project -ok 580 - Given I am in t/samples/hello_world/ +# Scenario number of attributes in the "Animals" project +ok 580 - Given I am in t/samples/polygons/java # ok 581 - When I run "analizo metrics ." # -ok 582 - Then the output must match "acc_mean:" -# -ok 583 - Then the output must match "acc_mode:" -# -ok 584 - Then the output must match "acc_standard_deviation:" -# -ok 585 - Then the output must match "acc_sum:" +ok 582 - Then analizo must report that module Polygon has npm = 3 # -ok 586 - Then the output must match "acc_variance:" +# Scenario number of attributes in the "Animals" project +ok 583 - Given I am in t/samples/polygons/csharp # -ok 587 - Then the output must match "acc_quantile_min:" +ok 584 - When I run "analizo metrics ." # -ok 588 - Then the output must match "acc_quantile_lower:" +ok 585 - Then analizo must report that module Polygon has npm = 2 # -ok 589 - Then the output must match "acc_quantile_median:" +# Scenario number of attributes in the "Animals" project +ok 586 - Given I am in t/samples/animals/cpp # -ok 590 - Then the output must match "acc_quantile_upper:" +ok 587 - When I run "analizo metrics ." # -ok 591 - Then the output must match "acc_quantile_max:" +ok 588 - Then analizo must report that module Animal has npm = 1 # -ok 592 - Then the output must match "acc_kurtosis:" +# Scenario number of attributes in the "Animals" project +ok 589 - Given I am in t/samples/animals/cpp # -ok 593 - Then the output must match "acc_skewness:" +ok 590 - When I run "analizo metrics ." # -# Scenario "Hello, world" project -ok 594 - Given I am in t/samples/hello_world/ +ok 591 - Then analizo must report that module Cat has npm = 2 # -ok 595 - When I run "analizo metrics ." +# Scenario number of attributes in the "Animals" project +ok 592 - Given I am in t/samples/animals/cpp # -ok 596 - Then the output must match "accm_mean:" +ok 593 - When I run "analizo metrics ." # -ok 597 - Then the output must match "accm_mode:" +ok 594 - Then analizo must report that module Dog has npm = 2 # -ok 598 - Then the output must match "accm_standard_deviation:" +# Scenario number of attributes in the "Animals" project +ok 595 - Given I am in t/samples/animals/java # -ok 599 - Then the output must match "accm_sum:" +ok 596 - When I run "analizo metrics ." # -ok 600 - Then the output must match "accm_variance:" +ok 597 - Then analizo must report that module Animal has npm = 1 # -ok 601 - Then the output must match "accm_quantile_min:" +# Scenario number of attributes in the "Animals" project +ok 598 - Given I am in t/samples/animals/java # -ok 602 - Then the output must match "accm_quantile_lower:" +ok 599 - When I run "analizo metrics ." # -ok 603 - Then the output must match "accm_quantile_median:" +ok 600 - Then analizo must report that module Cat has npm = 2 # -ok 604 - Then the output must match "accm_quantile_upper:" +# Scenario number of attributes in the "Animals" project +ok 601 - Given I am in t/samples/animals/java # -ok 605 - Then the output must match "accm_quantile_max:" +ok 602 - When I run "analizo metrics ." # -ok 606 - Then the output must match "accm_kurtosis:" +ok 603 - Then analizo must report that module Dog has npm = 2 # -ok 607 - Then the output must match "accm_skewness:" +# Scenario number of attributes in the "Animals" project +ok 604 - Given I am in t/samples/animals/csharp # -# Scenario "Hello, world" project -ok 608 - Given I am in t/samples/hello_world/ +ok 605 - When I run "analizo metrics ." # -ok 609 - When I run "analizo metrics ." +ok 606 - Then analizo must report that module Animal has npm = 1 # -ok 610 - Then the output must match "amloc_mean:" +# Scenario number of attributes in the "Animals" project +ok 607 - Given I am in t/samples/animals/csharp # -ok 611 - Then the output must match "amloc_mode:" +ok 608 - When I run "analizo metrics ." # -ok 612 - Then the output must match "amloc_standard_deviation:" +ok 609 - Then analizo must report that module Cat has npm = 2 # -ok 613 - Then the output must match "amloc_sum:" +# Scenario number of attributes in the "Animals" project +ok 610 - Given I am in t/samples/animals/csharp # -ok 614 - Then the output must match "amloc_variance:" +ok 611 - When I run "analizo metrics ." # -ok 615 - Then the output must match "amloc_quantile_min:" +ok 612 - Then analizo must report that module Dog has npm = 2 # -ok 616 - Then the output must match "amloc_quantile_lower:" +# Feature total number of methods per abstract class +# As a software developer I want analizo to report the number of abstract classes in my code So that I can evaluate it +# Scenario "Hello, world" project +ok 613 - Given I am in t/samples/hello_world/cpp # -ok 617 - Then the output must match "amloc_quantile_median:" +ok 614 - When I run "analizo metrics ." # -ok 618 - Then the output must match "amloc_quantile_upper:" +ok 615 - Then analizo must report that the project has total_methods_per_abstract_class = 0 # -ok 619 - Then the output must match "amloc_quantile_max:" +# Scenario "Hello, world" project +ok 616 - Given I am in t/samples/hello_world/java # -ok 620 - Then the output must match "amloc_kurtosis:" +ok 617 - When I run "analizo metrics ." # -ok 621 - Then the output must match "amloc_skewness:" +ok 618 - Then analizo must report that the project has total_methods_per_abstract_class = 0 # # Scenario "Hello, world" project -ok 622 - Given I am in t/samples/hello_world/ -# -ok 623 - When I run "analizo metrics ." +ok 619 - Given I am in t/samples/hello_world/csharp # -ok 624 - Then the output must match "anpm_mean:" +ok 620 - When I run "analizo metrics ." # -ok 625 - Then the output must match "anpm_mode:" +ok 621 - Then analizo must report that the project has total_methods_per_abstract_class = 0 # -ok 626 - Then the output must match "anpm_standard_deviation:" +# Scenario "Animals" project +ok 622 - Given I am in t/samples/animals/cpp # -ok 627 - Then the output must match "anpm_sum:" +ok 623 - When I run "analizo metrics ." # -ok 628 - Then the output must match "anpm_variance:" +ok 624 - Then analizo must report that the project has total_methods_per_abstract_class = 1 # -ok 629 - Then the output must match "anpm_quantile_min:" +# Scenario "Animals" project +ok 625 - Given I am in t/samples/animals/java # -ok 630 - Then the output must match "anpm_quantile_lower:" +ok 626 - When I run "analizo metrics ." # -ok 631 - Then the output must match "anpm_quantile_median:" +ok 627 - Then analizo must report that the project has total_methods_per_abstract_class = 1 # -ok 632 - Then the output must match "anpm_quantile_upper:" +# Scenario "Animals" project +ok 628 - Given I am in t/samples/animals/csharp # -ok 633 - Then the output must match "anpm_quantile_max:" +ok 629 - When I run "analizo metrics ." # -ok 634 - Then the output must match "anpm_kurtosis:" +ok 630 - Then analizo must report that the project has total_methods_per_abstract_class = 1 # -ok 635 - Then the output must match "anpm_skewness:" +# Scenario "Polygons" project +ok 631 - Given I am in t/samples/polygons/cpp # -# Scenario "Hello, world" project -ok 636 - Given I am in t/samples/hello_world/ +ok 632 - When I run "analizo metrics ." # -ok 637 - When I run "analizo metrics ." +ok 633 - Then analizo must report that the project has total_methods_per_abstract_class = 2.5 # -ok 638 - Then the output must match "cbo_mean:" +# Scenario "Polygons" project +ok 634 - Given I am in t/samples/polygons/java # -ok 639 - Then the output must match "cbo_mode:" +ok 635 - When I run "analizo metrics ." # -ok 640 - Then the output must match "cbo_standard_deviation:" +ok 636 - Then analizo must report that the project has total_methods_per_abstract_class = 2 # -ok 641 - Then the output must match "cbo_sum:" +# Scenario "Polygons" project +ok 637 - Given I am in t/samples/polygons/csharp # -ok 642 - Then the output must match "cbo_variance:" +ok 638 - When I run "analizo metrics ." # -ok 643 - Then the output must match "cbo_quantile_min:" +ok 639 - Then analizo must report that the project has total_methods_per_abstract_class = 2 # -ok 644 - Then the output must match "cbo_quantile_lower:" +# Feature number of abstract classes +# As a software developer I want analizo to report the number of modules with at least a defined method in my code So that I can evaluate it +# Scenario "Hello, world" project +ok 640 - Given I am in t/samples/hello_world/cpp # -ok 645 - Then the output must match "cbo_quantile_median:" +ok 641 - When I run "analizo metrics ." # -ok 646 - Then the output must match "cbo_quantile_upper:" +ok 642 - Then analizo must report that the project has total_modules_with_defined_attributes = 1 # -ok 647 - Then the output must match "cbo_quantile_max:" +# Scenario "Hello, world" project +ok 643 - Given I am in t/samples/hello_world/java # -ok 648 - Then the output must match "cbo_kurtosis:" +ok 644 - When I run "analizo metrics ." # -ok 649 - Then the output must match "cbo_skewness:" +ok 645 - Then analizo must report that the project has total_modules_with_defined_attributes = 1 # # Scenario "Hello, world" project -ok 650 - Given I am in t/samples/hello_world/ +ok 646 - Given I am in t/samples/hello_world/csharp # -ok 651 - When I run "analizo metrics ." +ok 647 - When I run "analizo metrics ." # -ok 652 - Then the output must match "dit_mean:" +ok 648 - Then analizo must report that the project has total_modules_with_defined_attributes = 1 # -ok 653 - Then the output must match "dit_mode:" -# -ok 654 - Then the output must match "dit_standard_deviation:" -# -ok 655 - Then the output must match "dit_sum:" +# Scenario "Animals" project +ok 649 - Given I am in t/samples/animals/cpp # -ok 656 - Then the output must match "dit_variance:" +ok 650 - When I run "analizo metrics ." # -ok 657 - Then the output must match "dit_quantile_min:" +ok 651 - Then analizo must report that the project has total_modules_with_defined_attributes = 2 # -ok 658 - Then the output must match "dit_quantile_lower:" +# Scenario "Animals" project +ok 652 - Given I am in t/samples/animals/java # -ok 659 - Then the output must match "dit_quantile_median:" +ok 653 - When I run "analizo metrics ." # -ok 660 - Then the output must match "dit_quantile_upper:" +ok 654 - Then analizo must report that the project has total_modules_with_defined_attributes = 2 # -ok 661 - Then the output must match "dit_quantile_max:" +# Scenario "Animals" project +ok 655 - Given I am in t/samples/animals/csharp # -ok 662 - Then the output must match "dit_kurtosis:" +ok 656 - When I run "analizo metrics ." # -ok 663 - Then the output must match "dit_skewness:" +ok 657 - Then analizo must report that the project has total_modules_with_defined_attributes = 2 # +# Feature output statistics values of metrics +# As a researcher I want to ouput statistics values of metrics So that I can evaluate a project at once # Scenario "Hello, world" project -ok 664 - Given I am in t/samples/hello_world/ +ok 658 - Given I am in t/samples/hello_world/ # -ok 665 - When I run "analizo metrics ." +ok 659 - When I run "analizo metrics ." # -ok 666 - Then the output must match "lcom4_mean:" +ok 660 - Then the output must match "acc_mean:" # -ok 667 - Then the output must match "lcom4_mode:" +ok 661 - Then the output must match "acc_mode:" # -ok 668 - Then the output must match "lcom4_standard_deviation:" +ok 662 - Then the output must match "acc_standard_deviation:" # -ok 669 - Then the output must match "lcom4_sum:" +ok 663 - Then the output must match "acc_sum:" # -ok 670 - Then the output must match "lcom4_variance:" +ok 664 - Then the output must match "acc_variance:" # -ok 671 - Then the output must match "lcom4_quantile_min:" +ok 665 - Then the output must match "acc_quantile_min:" # -ok 672 - Then the output must match "lcom4_quantile_lower:" +ok 666 - Then the output must match "acc_quantile_lower:" # -ok 673 - Then the output must match "lcom4_quantile_median:" +ok 667 - Then the output must match "acc_quantile_median:" # -ok 674 - Then the output must match "lcom4_quantile_upper:" +ok 668 - Then the output must match "acc_quantile_upper:" # -ok 675 - Then the output must match "lcom4_quantile_max:" +ok 669 - Then the output must match "acc_quantile_max:" # -ok 676 - Then the output must match "lcom4_kurtosis:" +ok 670 - Then the output must match "acc_kurtosis:" # -ok 677 - Then the output must match "lcom4_skewness:" +ok 671 - Then the output must match "acc_skewness:" # # Scenario "Hello, world" project -ok 678 - Given I am in t/samples/hello_world/ +ok 672 - Given I am in t/samples/hello_world/ # -ok 679 - When I run "analizo metrics ." +ok 673 - When I run "analizo metrics ." # -ok 680 - Then the output must match "loc_mean:" +ok 674 - Then the output must match "accm_mean:" # -ok 681 - Then the output must match "loc_mode:" +ok 675 - Then the output must match "accm_mode:" # -ok 682 - Then the output must match "loc_standard_deviation:" +ok 676 - Then the output must match "accm_standard_deviation:" # -ok 683 - Then the output must match "loc_sum:" +ok 677 - Then the output must match "accm_sum:" # -ok 684 - Then the output must match "loc_variance:" +ok 678 - Then the output must match "accm_variance:" # -ok 685 - Then the output must match "loc_quantile_min:" +ok 679 - Then the output must match "accm_quantile_min:" # -ok 686 - Then the output must match "loc_quantile_lower:" +ok 680 - Then the output must match "accm_quantile_lower:" # -ok 687 - Then the output must match "loc_quantile_median:" +ok 681 - Then the output must match "accm_quantile_median:" # -ok 688 - Then the output must match "loc_quantile_upper:" +ok 682 - Then the output must match "accm_quantile_upper:" # -ok 689 - Then the output must match "loc_quantile_max:" +ok 683 - Then the output must match "accm_quantile_max:" # -ok 690 - Then the output must match "loc_kurtosis:" +ok 684 - Then the output must match "accm_kurtosis:" # -ok 691 - Then the output must match "loc_skewness:" +ok 685 - Then the output must match "accm_skewness:" # # Scenario "Hello, world" project -ok 692 - Given I am in t/samples/hello_world/ +ok 686 - Given I am in t/samples/hello_world/ # -ok 693 - When I run "analizo metrics ." +ok 687 - When I run "analizo metrics ." # -ok 694 - Then the output must match "mmloc_mean:" +ok 688 - Then the output must match "amloc_mean:" # -ok 695 - Then the output must match "mmloc_mode:" +ok 689 - Then the output must match "amloc_mode:" # -ok 696 - Then the output must match "mmloc_standard_deviation:" +ok 690 - Then the output must match "amloc_standard_deviation:" # -ok 697 - Then the output must match "mmloc_sum:" +ok 691 - Then the output must match "amloc_sum:" # -ok 698 - Then the output must match "mmloc_variance:" +ok 692 - Then the output must match "amloc_variance:" # -ok 699 - Then the output must match "mmloc_quantile_min:" +ok 693 - Then the output must match "amloc_quantile_min:" # -ok 700 - Then the output must match "mmloc_quantile_lower:" +ok 694 - Then the output must match "amloc_quantile_lower:" # -ok 701 - Then the output must match "mmloc_quantile_median:" +ok 695 - Then the output must match "amloc_quantile_median:" # -ok 702 - Then the output must match "mmloc_quantile_upper:" +ok 696 - Then the output must match "amloc_quantile_upper:" # -ok 703 - Then the output must match "mmloc_quantile_max:" +ok 697 - Then the output must match "amloc_quantile_max:" # -ok 704 - Then the output must match "mmloc_kurtosis:" +ok 698 - Then the output must match "amloc_kurtosis:" # -ok 705 - Then the output must match "mmloc_skewness:" +ok 699 - Then the output must match "amloc_skewness:" # # Scenario "Hello, world" project -ok 706 - Given I am in t/samples/hello_world/ +ok 700 - Given I am in t/samples/hello_world/ # -ok 707 - When I run "analizo metrics ." +ok 701 - When I run "analizo metrics ." # -ok 708 - Then the output must match "noa_mean:" +ok 702 - Then the output must match "anpm_mean:" # -ok 709 - Then the output must match "noa_mode:" +ok 703 - Then the output must match "anpm_mode:" # -ok 710 - Then the output must match "noa_standard_deviation:" +ok 704 - Then the output must match "anpm_standard_deviation:" # -ok 711 - Then the output must match "noa_sum:" +ok 705 - Then the output must match "anpm_sum:" # -ok 712 - Then the output must match "noa_variance:" +ok 706 - Then the output must match "anpm_variance:" # -ok 713 - Then the output must match "noa_quantile_min:" +ok 707 - Then the output must match "anpm_quantile_min:" # -ok 714 - Then the output must match "noa_quantile_lower:" +ok 708 - Then the output must match "anpm_quantile_lower:" # -ok 715 - Then the output must match "noa_quantile_median:" +ok 709 - Then the output must match "anpm_quantile_median:" # -ok 716 - Then the output must match "noa_quantile_upper:" +ok 710 - Then the output must match "anpm_quantile_upper:" # -ok 717 - Then the output must match "noa_quantile_max:" +ok 711 - Then the output must match "anpm_quantile_max:" # -ok 718 - Then the output must match "noa_kurtosis:" +ok 712 - Then the output must match "anpm_kurtosis:" # -ok 719 - Then the output must match "noa_skewness:" +ok 713 - Then the output must match "anpm_skewness:" # # Scenario "Hello, world" project -ok 720 - Given I am in t/samples/hello_world/ +ok 714 - Given I am in t/samples/hello_world/ # -ok 721 - When I run "analizo metrics ." +ok 715 - When I run "analizo metrics ." # -ok 722 - Then the output must match "noc_mean:" +ok 716 - Then the output must match "cbo_mean:" # -ok 723 - Then the output must match "noc_mode:" +ok 717 - Then the output must match "cbo_mode:" # -ok 724 - Then the output must match "noc_standard_deviation:" +ok 718 - Then the output must match "cbo_standard_deviation:" # -ok 725 - Then the output must match "noc_sum:" +ok 719 - Then the output must match "cbo_sum:" # -ok 726 - Then the output must match "noc_variance:" +ok 720 - Then the output must match "cbo_variance:" # -ok 727 - Then the output must match "noc_quantile_min:" +ok 721 - Then the output must match "cbo_quantile_min:" # -ok 728 - Then the output must match "noc_quantile_lower:" +ok 722 - Then the output must match "cbo_quantile_lower:" # -ok 729 - Then the output must match "noc_quantile_median:" +ok 723 - Then the output must match "cbo_quantile_median:" # -ok 730 - Then the output must match "noc_quantile_upper:" +ok 724 - Then the output must match "cbo_quantile_upper:" # -ok 731 - Then the output must match "noc_quantile_max:" +ok 725 - Then the output must match "cbo_quantile_max:" # -ok 732 - Then the output must match "noc_kurtosis:" +ok 726 - Then the output must match "cbo_kurtosis:" # -ok 733 - Then the output must match "noc_skewness:" +ok 727 - Then the output must match "cbo_skewness:" # # Scenario "Hello, world" project -ok 734 - Given I am in t/samples/hello_world/ +ok 728 - Given I am in t/samples/hello_world/ # -ok 735 - When I run "analizo metrics ." +ok 729 - When I run "analizo metrics ." # -ok 736 - Then the output must match "nom_mean:" +ok 730 - Then the output must match "dit_mean:" # -ok 737 - Then the output must match "nom_mode:" +ok 731 - Then the output must match "dit_mode:" # -ok 738 - Then the output must match "nom_standard_deviation:" +ok 732 - Then the output must match "dit_standard_deviation:" # -ok 739 - Then the output must match "nom_sum:" +ok 733 - Then the output must match "dit_sum:" # -ok 740 - Then the output must match "nom_variance:" +ok 734 - Then the output must match "dit_variance:" # -ok 741 - Then the output must match "nom_quantile_min:" +ok 735 - Then the output must match "dit_quantile_min:" # -ok 742 - Then the output must match "nom_quantile_lower:" +ok 736 - Then the output must match "dit_quantile_lower:" # -ok 743 - Then the output must match "nom_quantile_median:" +ok 737 - Then the output must match "dit_quantile_median:" # -ok 744 - Then the output must match "nom_quantile_upper:" +ok 738 - Then the output must match "dit_quantile_upper:" # -ok 745 - Then the output must match "nom_quantile_max:" +ok 739 - Then the output must match "dit_quantile_max:" # -ok 746 - Then the output must match "nom_kurtosis:" +ok 740 - Then the output must match "dit_kurtosis:" # -ok 747 - Then the output must match "nom_skewness:" +ok 741 - Then the output must match "dit_skewness:" # # Scenario "Hello, world" project -ok 748 - Given I am in t/samples/hello_world/ +ok 742 - Given I am in t/samples/hello_world/ # -ok 749 - When I run "analizo metrics ." +ok 743 - When I run "analizo metrics ." # -ok 750 - Then the output must match "npm_mean:" +ok 744 - Then the output must match "lcom4_mean:" # -ok 751 - Then the output must match "npm_mode:" +ok 745 - Then the output must match "lcom4_mode:" # -ok 752 - Then the output must match "npm_standard_deviation:" +ok 746 - Then the output must match "lcom4_standard_deviation:" # -ok 753 - Then the output must match "npm_sum:" +ok 747 - Then the output must match "lcom4_sum:" # -ok 754 - Then the output must match "npm_variance:" +ok 748 - Then the output must match "lcom4_variance:" # -ok 755 - Then the output must match "npm_quantile_min:" +ok 749 - Then the output must match "lcom4_quantile_min:" # -ok 756 - Then the output must match "npm_quantile_lower:" +ok 750 - Then the output must match "lcom4_quantile_lower:" # -ok 757 - Then the output must match "npm_quantile_median:" +ok 751 - Then the output must match "lcom4_quantile_median:" # -ok 758 - Then the output must match "npm_quantile_upper:" +ok 752 - Then the output must match "lcom4_quantile_upper:" # -ok 759 - Then the output must match "npm_quantile_max:" +ok 753 - Then the output must match "lcom4_quantile_max:" # -ok 760 - Then the output must match "npm_kurtosis:" +ok 754 - Then the output must match "lcom4_kurtosis:" # -ok 761 - Then the output must match "npm_skewness:" +ok 755 - Then the output must match "lcom4_skewness:" # # Scenario "Hello, world" project -ok 762 - Given I am in t/samples/hello_world/ +ok 756 - Given I am in t/samples/hello_world/ # -ok 763 - When I run "analizo metrics ." +ok 757 - When I run "analizo metrics ." # -ok 764 - Then the output must match "npa_mean:" +ok 758 - Then the output must match "loc_mean:" # -ok 765 - Then the output must match "npa_mode:" +ok 759 - Then the output must match "loc_mode:" # -ok 766 - Then the output must match "npa_standard_deviation:" +ok 760 - Then the output must match "loc_standard_deviation:" # -ok 767 - Then the output must match "npa_sum:" +ok 761 - Then the output must match "loc_sum:" # -ok 768 - Then the output must match "npa_variance:" +ok 762 - Then the output must match "loc_variance:" # -ok 769 - Then the output must match "npa_quantile_min:" +ok 763 - Then the output must match "loc_quantile_min:" # -ok 770 - Then the output must match "npa_quantile_lower:" +ok 764 - Then the output must match "loc_quantile_lower:" # -ok 771 - Then the output must match "npa_quantile_median:" +ok 765 - Then the output must match "loc_quantile_median:" # -ok 772 - Then the output must match "npa_quantile_upper:" +ok 766 - Then the output must match "loc_quantile_upper:" # -ok 773 - Then the output must match "npa_quantile_max:" +ok 767 - Then the output must match "loc_quantile_max:" # -ok 774 - Then the output must match "npa_kurtosis:" +ok 768 - Then the output must match "loc_kurtosis:" # -ok 775 - Then the output must match "npa_skewness:" +ok 769 - Then the output must match "loc_skewness:" # # Scenario "Hello, world" project -ok 776 - Given I am in t/samples/hello_world/ +ok 770 - Given I am in t/samples/hello_world/ # -ok 777 - When I run "analizo metrics ." +ok 771 - When I run "analizo metrics ." # -ok 778 - Then the output must match "rfc_mean:" +ok 772 - Then the output must match "mmloc_mean:" # -ok 779 - Then the output must match "rfc_mode:" +ok 773 - Then the output must match "mmloc_mode:" # -ok 780 - Then the output must match "rfc_standard_deviation:" +ok 774 - Then the output must match "mmloc_standard_deviation:" # -ok 781 - Then the output must match "rfc_sum:" +ok 775 - Then the output must match "mmloc_sum:" # -ok 782 - Then the output must match "rfc_variance:" +ok 776 - Then the output must match "mmloc_variance:" # -ok 783 - Then the output must match "rfc_quantile_min:" +ok 777 - Then the output must match "mmloc_quantile_min:" # -ok 784 - Then the output must match "rfc_quantile_lower:" +ok 778 - Then the output must match "mmloc_quantile_lower:" # -ok 785 - Then the output must match "rfc_quantile_median:" +ok 779 - Then the output must match "mmloc_quantile_median:" # -ok 786 - Then the output must match "rfc_quantile_upper:" +ok 780 - Then the output must match "mmloc_quantile_upper:" # -ok 787 - Then the output must match "rfc_quantile_max:" +ok 781 - Then the output must match "mmloc_quantile_max:" # -ok 788 - Then the output must match "rfc_kurtosis:" +ok 782 - Then the output must match "mmloc_kurtosis:" # -ok 789 - Then the output must match "rfc_skewness:" +ok 783 - Then the output must match "mmloc_skewness:" # # Scenario "Hello, world" project -ok 790 - Given I am in t/samples/hello_world/ +ok 784 - Given I am in t/samples/hello_world/ # -ok 791 - When I run "analizo metrics ." +ok 785 - When I run "analizo metrics ." # -ok 792 - Then the output must match "sc_mean:" +ok 786 - Then the output must match "noa_mean:" # -ok 793 - Then the output must match "sc_mode:" +ok 787 - Then the output must match "noa_mode:" # -ok 794 - Then the output must match "sc_standard_deviation:" +ok 788 - Then the output must match "noa_standard_deviation:" # -ok 795 - Then the output must match "sc_sum:" +ok 789 - Then the output must match "noa_sum:" # -ok 796 - Then the output must match "sc_variance:" +ok 790 - Then the output must match "noa_variance:" # -ok 797 - Then the output must match "sc_quantile_min:" +ok 791 - Then the output must match "noa_quantile_min:" # -ok 798 - Then the output must match "sc_quantile_lower:" +ok 792 - Then the output must match "noa_quantile_lower:" # -ok 799 - Then the output must match "sc_quantile_median:" +ok 793 - Then the output must match "noa_quantile_median:" # -ok 800 - Then the output must match "sc_quantile_upper:" +ok 794 - Then the output must match "noa_quantile_upper:" # -ok 801 - Then the output must match "sc_quantile_max:" +ok 795 - Then the output must match "noa_quantile_max:" # -ok 802 - Then the output must match "sc_kurtosis:" +ok 796 - Then the output must match "noa_kurtosis:" # -ok 803 - Then the output must match "sc_skewness:" +ok 797 - Then the output must match "noa_skewness:" # -# Feature output file for metrics tool -# Scenario passing output file in the command line -ok 804 - Given I am in . +# Scenario "Hello, world" project +ok 798 - Given I am in t/samples/hello_world/ # -ok 805 - When I run "analizo metrics --output output.yml.tmp t/samples/sample_basic/" +ok 799 - When I run "analizo metrics ." # -ok 806 - Then the contents of "output.yml.tmp" must match "module2" +ok 800 - Then the output must match "noc_mean:" # -ok 807 - And the exit status must be 0 +ok 801 - Then the output must match "noc_mode:" # -# Scenario passing output file without permission to write -ok 808 - Given I am in . +ok 802 - Then the output must match "noc_standard_deviation:" # -ok 809 - When I run "touch output.tmp" +ok 803 - Then the output must match "noc_sum:" # -ok 810 - And I run "chmod 000 output.tmp" +ok 804 - Then the output must match "noc_variance:" # -ok 811 - And I run "analizo metrics --output output.tmp t/samples/sample_basic/" +ok 805 - Then the output must match "noc_quantile_min:" # -ok 812 - Then the exit status must not be 0 +ok 806 - Then the output must match "noc_quantile_lower:" # -ok 813 - And analizo must emit a warning matching "Permission denied" +ok 807 - Then the output must match "noc_quantile_median:" # -# Scenario passing output file in an unexisting directory -ok 814 - Given I am in . +ok 808 - Then the output must match "noc_quantile_upper:" # -ok 815 - When I run "analizo metrics --output /this/directory/must/not/exists/output.yml t/samples" +ok 809 - Then the output must match "noc_quantile_max:" # -ok 816 - Then the exit status must not be 0 +ok 810 - Then the output must match "noc_kurtosis:" # -ok 817 - And analizo must emit a warning matching "No such file or directory" +ok 811 - Then the output must match "noc_skewness:" # -# Feature average cyclomatic complexity per method -# As a software developer I want to calculate the average cyclomatic complexity per method of my code So that I can spot the more complex modules and refactor them -# Scenario my "conditionals" C project -ok 818 - Given I am in t/samples/conditionals/c +# Scenario "Hello, world" project +ok 812 - Given I am in t/samples/hello_world/ # -ok 819 - When I run "analizo metrics ." +ok 813 - When I run "analizo metrics ." # -ok 820 - Then analizo must report that module cc1 has accm = 1 +ok 814 - Then the output must match "nom_mean:" # -ok 821 - Then analizo must report that module cc2 has accm = 2 +ok 815 - Then the output must match "nom_mode:" # -ok 822 - Then analizo must report that module cc3 has accm = 3 +ok 816 - Then the output must match "nom_standard_deviation:" # -ok 823 - Then analizo must report that module cc4 has accm = 4 +ok 817 - Then the output must match "nom_sum:" # -# Scenario my "conditionals" C project -ok 824 - Given I am in t/samples/conditionals/csharp +ok 818 - Then the output must match "nom_variance:" # -ok 825 - When I run "analizo metrics ." +ok 819 - Then the output must match "nom_quantile_min:" # -ok 826 - Then analizo must report that module cc1 has accm = 1 +ok 820 - Then the output must match "nom_quantile_lower:" # -ok 827 - Then analizo must report that module cc2 has accm = 2 +ok 821 - Then the output must match "nom_quantile_median:" # -ok 828 - Then analizo must report that module cc3 has accm = 3 +ok 822 - Then the output must match "nom_quantile_upper:" # -ok 829 - Then analizo must report that module cc4 has accm = 4 +ok 823 - Then the output must match "nom_quantile_max:" # -# Feature list metrics -# As a Research or Practioner I want to extract metrics from source code So that I can learn, understand and evaluate it -# Scenario listing metrics -ok 830 - When I run "analizo metrics --list" +ok 824 - Then the output must match "nom_kurtosis:" # -ok 831 - Then analizo must present a list of metrics +ok 825 - Then the output must match "nom_skewness:" # -# Scenario listing metrics -ok 832 - When I run "analizo metrics -l" +# Scenario "Hello, world" project +ok 826 - Given I am in t/samples/hello_world/ # -ok 833 - Then analizo must present a list of metrics +ok 827 - When I run "analizo metrics ." # -# Feature output only global metrics -# As a researcher I want to ouput only the global metrics So that I can evaluate several projects at once -# Scenario simple case -ok 834 - Given I am in t/samples/sample_basic/c/ +ok 828 - Then the output must match "npm_mean:" # -ok 835 - When I run "analizo metrics --global-only ." +ok 829 - Then the output must match "npm_mode:" # -ok 836 - Then the output must match "cbo_mean:" +ok 830 - Then the output must match "npm_standard_deviation:" # -ok 837 - And the output must not match "_module:" +ok 831 - Then the output must match "npm_sum:" # -# Scenario short version -ok 838 - Given I am in t/samples/sample_basic/c/ +ok 832 - Then the output must match "npm_variance:" # -ok 839 - When I run "analizo metrics -g ." +ok 833 - Then the output must match "npm_quantile_min:" # -ok 840 - Then the output must match "cbo_mean:" +ok 834 - Then the output must match "npm_quantile_lower:" # -ok 841 - And the output must not match "_module:" +ok 835 - Then the output must match "npm_quantile_median:" # -# Feature number of public methods metric -# As a software developer I want to calculate the number of public methods per module metric So that I can evaluate my code -# Scenario number of attributes in the "Animals" project -ok 842 - Given I am in t/samples/polygons/cpp +ok 836 - Then the output must match "npm_quantile_upper:" # -ok 843 - When I run "analizo metrics ." +ok 837 - Then the output must match "npm_quantile_max:" # -ok 844 - Then analizo must report that module CPolygon has npm = 2 +ok 838 - Then the output must match "npm_kurtosis:" # -# Scenario number of attributes in the "Animals" project -ok 845 - Given I am in t/samples/polygons/cpp +ok 839 - Then the output must match "npm_skewness:" # -ok 846 - When I run "analizo metrics ." +# Scenario "Hello, world" project +ok 840 - Given I am in t/samples/hello_world/ # -ok 847 - Then analizo must report that module CTetragon has npm = 1 +ok 841 - When I run "analizo metrics ." # -# Scenario number of attributes in the "Animals" project -ok 848 - Given I am in t/samples/polygons/java +ok 842 - Then the output must match "npa_mean:" # -ok 849 - When I run "analizo metrics ." +ok 843 - Then the output must match "npa_mode:" # -ok 850 - Then analizo must report that module Polygon has npm = 3 +ok 844 - Then the output must match "npa_standard_deviation:" # -# Scenario number of attributes in the "Animals" project -ok 851 - Given I am in t/samples/polygons/csharp +ok 845 - Then the output must match "npa_sum:" # -ok 852 - When I run "analizo metrics ." +ok 846 - Then the output must match "npa_variance:" # -ok 853 - Then analizo must report that module Polygon has npm = 2 +ok 847 - Then the output must match "npa_quantile_min:" # -# Scenario number of attributes in the "Animals" project -ok 854 - Given I am in t/samples/animals/cpp +ok 848 - Then the output must match "npa_quantile_lower:" # -ok 855 - When I run "analizo metrics ." +ok 849 - Then the output must match "npa_quantile_median:" # -ok 856 - Then analizo must report that module Animal has npm = 1 +ok 850 - Then the output must match "npa_quantile_upper:" # -# Scenario number of attributes in the "Animals" project -ok 857 - Given I am in t/samples/animals/cpp +ok 851 - Then the output must match "npa_quantile_max:" # -ok 858 - When I run "analizo metrics ." +ok 852 - Then the output must match "npa_kurtosis:" # -ok 859 - Then analizo must report that module Cat has npm = 2 +ok 853 - Then the output must match "npa_skewness:" # -# Scenario number of attributes in the "Animals" project -ok 860 - Given I am in t/samples/animals/cpp +# Scenario "Hello, world" project +ok 854 - Given I am in t/samples/hello_world/ # -ok 861 - When I run "analizo metrics ." +ok 855 - When I run "analizo metrics ." # -ok 862 - Then analizo must report that module Dog has npm = 2 +ok 856 - Then the output must match "rfc_mean:" # -# Scenario number of attributes in the "Animals" project -ok 863 - Given I am in t/samples/animals/java +ok 857 - Then the output must match "rfc_mode:" # -ok 864 - When I run "analizo metrics ." +ok 858 - Then the output must match "rfc_standard_deviation:" # -ok 865 - Then analizo must report that module Animal has npm = 1 +ok 859 - Then the output must match "rfc_sum:" # -# Scenario number of attributes in the "Animals" project -ok 866 - Given I am in t/samples/animals/java +ok 860 - Then the output must match "rfc_variance:" # -ok 867 - When I run "analizo metrics ." +ok 861 - Then the output must match "rfc_quantile_min:" # -ok 868 - Then analizo must report that module Cat has npm = 2 +ok 862 - Then the output must match "rfc_quantile_lower:" # -# Scenario number of attributes in the "Animals" project -ok 869 - Given I am in t/samples/animals/java +ok 863 - Then the output must match "rfc_quantile_median:" # -ok 870 - When I run "analizo metrics ." +ok 864 - Then the output must match "rfc_quantile_upper:" # -ok 871 - Then analizo must report that module Dog has npm = 2 +ok 865 - Then the output must match "rfc_quantile_max:" # -# Scenario number of attributes in the "Animals" project -ok 872 - Given I am in t/samples/animals/csharp +ok 866 - Then the output must match "rfc_kurtosis:" # -ok 873 - When I run "analizo metrics ." +ok 867 - Then the output must match "rfc_skewness:" # -ok 874 - Then analizo must report that module Animal has npm = 1 +# Scenario "Hello, world" project +ok 868 - Given I am in t/samples/hello_world/ # -# Scenario number of attributes in the "Animals" project -ok 875 - Given I am in t/samples/animals/csharp +ok 869 - When I run "analizo metrics ." # -ok 876 - When I run "analizo metrics ." +ok 870 - Then the output must match "sc_mean:" # -ok 877 - Then analizo must report that module Cat has npm = 2 +ok 871 - Then the output must match "sc_mode:" # -# Scenario number of attributes in the "Animals" project -ok 878 - Given I am in t/samples/animals/csharp +ok 872 - Then the output must match "sc_standard_deviation:" # -ok 879 - When I run "analizo metrics ." +ok 873 - Then the output must match "sc_sum:" # -ok 880 - Then analizo must report that module Dog has npm = 2 +ok 874 - Then the output must match "sc_variance:" # -# Feature change cost degree -# As a software developer I want analizo to report the degree of change cost in my code So that I can evaluate it -# Scenario "Hello, world" project -ok 881 - Given I am in t/samples/hello_world/cpp +ok 875 - Then the output must match "sc_quantile_min:" # -ok 882 - When I run "analizo metrics ." +ok 876 - Then the output must match "sc_quantile_lower:" # -ok 883 - Then analizo must report that the project has change_cost = 0.75 +ok 877 - Then the output must match "sc_quantile_median:" # -# Scenario "Hello, world" project -ok 884 - Given I am in t/samples/hello_world/java +ok 878 - Then the output must match "sc_quantile_upper:" # -ok 885 - When I run "analizo metrics ." +ok 879 - Then the output must match "sc_quantile_max:" # -ok 886 - Then analizo must report that the project has change_cost = 0.75 +ok 880 - Then the output must match "sc_kurtosis:" # -# Scenario "Hello, world" project -ok 887 - Given I am in t/samples/hello_world/csharp +ok 881 - Then the output must match "sc_skewness:" # -ok 888 - When I run "analizo metrics ." +# Feature output file for metrics tool +# Scenario passing output file in the command line +ok 882 - Given I am in . # -ok 889 - Then analizo must report that the project has change_cost = 0.75 +ok 883 - When I run "analizo metrics --output output.yml.tmp t/samples/sample_basic/" # -# Scenario "Animals" project -ok 890 - Given I am in t/samples/animals/cpp +ok 884 - Then the contents of "output.yml.tmp" must match "module2" # -ok 891 - When I run "analizo metrics ." +ok 885 - And the exit status must be 0 # -ok 892 - Then analizo must report that the project has change_cost = 0.44 +# Scenario passing output file without permission to write +ok 886 - Given I am in . # -# Scenario "Animals" project -ok 893 - Given I am in t/samples/animals/java +ok 887 - When I run "touch output.tmp" # -ok 894 - When I run "analizo metrics ." +ok 888 - And I run "chmod 000 output.tmp" # -ok 895 - Then analizo must report that the project has change_cost = 0.44 +ok 889 - And I run "analizo metrics --output output.tmp t/samples/sample_basic/" # -# Scenario "Animals" project -ok 896 - Given I am in t/samples/animals/csharp +ok 890 - Then the exit status must not be 0 # -ok 897 - When I run "analizo metrics ." +ok 891 - And analizo must emit a warning matching "Permission denied" # -ok 898 - Then analizo must report that the project has change_cost = 0.44 +# Scenario passing output file in an unexisting directory +ok 892 - Given I am in . # -# Scenario "Hieracchical Graph" project -ok 899 - Given I am in t/samples/hierarchical_graph/c +ok 893 - When I run "analizo metrics --output /this/directory/must/not/exists/output.yml t/samples" # -ok 900 - When I run "analizo metrics ." +ok 894 - Then the exit status must not be 0 # -ok 901 - Then analizo must report that the project has change_cost = 0.42 +ok 895 - And analizo must emit a warning matching "No such file or directory" # -# Scenario "Hieracchical Graph" project -ok 902 - Given I am in t/samples/hierarchical_graph/csharp +# Feature language filters +# As a software developer in a multi-language project I want to analyze only one programming language So that the results are as correct as possible +# Scenario filtering for C code +ok 896 - Given I am in t/samples/mixed # -ok 903 - When I run "analizo metrics ." +ok 897 - When I run "analizo metrics --language c ." # -ok 904 - Then analizo must report that the project has change_cost = 0.28 +ok 898 - Then the output must match "native_backend" # -# Scenario "Cyclical Graph" project -ok 905 - Given I am in t/samples/cyclical_graph/c +ok 899 - And the output must not match "UI" # -ok 906 - When I run "analizo metrics ." +ok 900 - And the output must not match "Backend" # -ok 907 - Then analizo must report that the project has change_cost = 0.5 +ok 901 - And the output must not match "CSharp_Backend" # -# Scenario "Cyclical Graph" project -ok 908 - Given I am in t/samples/cyclical_graph/csharp +# Scenario filtering for Java code +ok 902 - Given I am in t/samples/mixed # -ok 909 - When I run "analizo metrics ." +ok 903 - When I run "analizo metrics --language java ." # -ok 910 - Then analizo must report that the project has change_cost = 0.36 +ok 904 - Then the output must match "UI" # -# Feature number of abstract classes -# As a software developer I want analizo to report the number of abstract classes in my code So that I can evaluate it -# Scenario "Hello, world" project -ok 911 - Given I am in t/samples/hello_world/cpp +ok 905 - And the output must match "Backend" # -ok 912 - When I run "analizo metrics ." +ok 906 - And the output must not match "native_backend" # -ok 913 - Then analizo must report that the project has total_abstract_classes = 0 +ok 907 - And the output must not match "CSharp_Backend" # -# Scenario "Hello, world" project -ok 914 - Given I am in t/samples/hello_world/java +# Scenario filtering for CSharp code +ok 908 - Given I am in t/samples/mixed # -ok 915 - When I run "analizo metrics ." +ok 909 - When I run "analizo metrics --language csharp ." # -ok 916 - Then analizo must report that the project has total_abstract_classes = 0 +ok 910 - Then the output must match "CSharp_Backend" # -# Scenario "Hello, world" project -ok 917 - Given I am in t/samples/hello_world/csharp +ok 911 - And the output must not match "UI" # -ok 918 - When I run "analizo metrics ." +ok 912 - And the output must not match "native_backend" # -ok 919 - Then analizo must report that the project has total_abstract_classes = 0 +# Scenario listing languages +ok 913 - When I run "analizo metrics --language list" # -# Scenario "Animals" project -ok 920 - Given I am in t/samples/animals/cpp +ok 914 - Then analizo must present a list of languages # -ok 921 - When I run "analizo metrics ." +# Feature total modules +# As a software developer I want analizo to report the total number of modules in my code So that I can evaluate it +# Scenario Java Enumeration sample +ok 915 - Given I am in t/samples/enumeration # -ok 922 - Then analizo must report that the project has total_abstract_classes = 2 +ok 916 - When I run "analizo metrics ." # -# Scenario "Animals" project -ok 923 - Given I am in t/samples/animals/java +ok 917 - Then analizo must report that the project has total_modules = 3 # -ok 924 - When I run "analizo metrics ." +# Feature average cyclomatic complexity per method +# As a software developer I want to calculate the average cyclomatic complexity per method of my code So that I can spot the more complex modules and refactor them +# Scenario my "conditionals" C project +ok 918 - Given I am in t/samples/conditionals/c # -ok 925 - Then analizo must report that the project has total_abstract_classes = 2 +ok 919 - When I run "analizo metrics ." # -# Scenario "Animals" project -ok 926 - Given I am in t/samples/animals/csharp +ok 920 - Then analizo must report that module cc1 has accm = 1 # -ok 927 - When I run "analizo metrics ." +ok 921 - Then analizo must report that module cc2 has accm = 2 # -ok 928 - Then analizo must report that the project has total_abstract_classes = 1 +ok 922 - Then analizo must report that module cc3 has accm = 3 # -# Scenario "Polygons" project -ok 929 - Given I am in t/samples/polygons/cpp +ok 923 - Then analizo must report that module cc4 has accm = 4 # -ok 930 - When I run "analizo metrics ." +# Scenario my "conditionals" C project +ok 924 - Given I am in t/samples/conditionals/csharp # -ok 931 - Then analizo must report that the project has total_abstract_classes = 2 +ok 925 - When I run "analizo metrics ." # -# Scenario "Polygons" project -ok 932 - Given I am in t/samples/polygons/java +ok 926 - Then analizo must report that module cc1 has accm = 1 # -ok 933 - When I run "analizo metrics ." +ok 927 - Then analizo must report that module cc2 has accm = 2 # -ok 934 - Then analizo must report that the project has total_abstract_classes = 2 +ok 928 - Then analizo must report that module cc3 has accm = 3 # -# Scenario "Polygons" project -ok 935 - Given I am in t/samples/polygons/csharp +ok 929 - Then analizo must report that module cc4 has accm = 4 # -ok 936 - When I run "analizo metrics ." +# Feature list metrics +# As a Research or Practioner I want to extract metrics from source code So that I can learn, understand and evaluate it +# Scenario listing metrics +ok 930 - When I run "analizo metrics --list" # -ok 937 - Then analizo must report that the project has total_abstract_classes = 2 +ok 931 - Then analizo must present a list of metrics # -# Scenario "AbstractClass" project -ok 938 - Given I am in t/samples/abstract_class/java +# Scenario listing metrics +ok 932 - When I run "analizo metrics -l" # -ok 939 - When I run "analizo metrics ." +ok 933 - Then analizo must present a list of metrics # -ok 940 - Then analizo must report that the project has total_abstract_classes = 1 +# Feature change cost degree +# As a software developer I want analizo to report the degree of change cost in my code So that I can evaluate it +# Scenario "Hello, world" project +ok 934 - Given I am in t/samples/hello_world/cpp # -ok 941 - And analizo must report that the project has total_methods_per_abstract_class = 6 +ok 935 - When I run "analizo metrics ." # -# Scenario "AbstractClass" project -ok 942 - Given I am in t/samples/abstract_class/csharp +ok 936 - Then analizo must report that the project has change_cost = 0.75 # -ok 943 - When I run "analizo metrics ." +# Scenario "Hello, world" project +ok 937 - Given I am in t/samples/hello_world/java # -ok 944 - Then analizo must report that the project has total_abstract_classes = 1 +ok 938 - When I run "analizo metrics ." # -ok 945 - And analizo must report that the project has total_methods_per_abstract_class = 1 +ok 939 - Then analizo must report that the project has change_cost = 0.75 # -# Feature coupling between objects -# As a software developer I want analizo to report the value of CBO metric in my code So that I can evaluate it # Scenario "Hello, world" project -ok 946 - Given I am in t/samples/hello_world/c +ok 940 - Given I am in t/samples/hello_world/csharp +# +ok 941 - When I run "analizo metrics ." +# +ok 942 - Then analizo must report that the project has change_cost = 0.75 +# +# Scenario "Animals" project +ok 943 - Given I am in t/samples/animals/cpp +# +ok 944 - When I run "analizo metrics ." +# +ok 945 - Then analizo must report that the project has change_cost = 0.44 +# +# Scenario "Animals" project +ok 946 - Given I am in t/samples/animals/java # ok 947 - When I run "analizo metrics ." # -ok 948 - Then analizo must report that module main has cbo = 1 +ok 948 - Then analizo must report that the project has change_cost = 0.44 # -# Scenario "Hello, world" project -ok 949 - Given I am in t/samples/hello_world/cpp +# Scenario "Animals" project +ok 949 - Given I am in t/samples/animals/csharp # ok 950 - When I run "analizo metrics ." # -ok 951 - Then analizo must report that module main has cbo = 1 +ok 951 - Then analizo must report that the project has change_cost = 0.44 # -# Scenario "Hello, world" project -ok 952 - Given I am in t/samples/hello_world/java +# Scenario "Hieracchical Graph" project +ok 952 - Given I am in t/samples/hierarchical_graph/c # ok 953 - When I run "analizo metrics ." # -ok 954 - Then analizo must report that module Main has cbo = 1 +ok 954 - Then analizo must report that the project has change_cost = 0.42 # -# Scenario "Hello, world" project -ok 955 - Given I am in t/samples/hello_world/csharp +# Scenario "Hieracchical Graph" project +ok 955 - Given I am in t/samples/hierarchical_graph/csharp # ok 956 - When I run "analizo metrics ." # -ok 957 - Then analizo must report that module main has cbo = 1 +ok 957 - Then analizo must report that the project has change_cost = 0.28 # -# Scenario "Animals" project -ok 958 - Given I am in t/samples/animals/cpp +# Scenario "Cyclical Graph" project +ok 958 - Given I am in t/samples/cyclical_graph/c # ok 959 - When I run "analizo metrics ." # -ok 960 - Then analizo must report that module main has cbo = 1 +ok 960 - Then analizo must report that the project has change_cost = 0.5 # -# Scenario "Animals" project -ok 961 - Given I am in t/samples/animals/cpp +# Scenario "Cyclical Graph" project +ok 961 - Given I am in t/samples/cyclical_graph/csharp # ok 962 - When I run "analizo metrics ." # -ok 963 - Then analizo must report that module mammal has cbo = 0 +ok 963 - Then analizo must report that the project has change_cost = 0.36 # -# Scenario "Animals" project -ok 964 - Given I am in t/samples/animals/java +# Feature number of attributes metric +# As a software developer I want to calculate the number of attributes per module metric So that I can evaluate my code +# Scenario number of attributes in the "Animals" project +ok 964 - Given I am in t/samples/animals/cpp # ok 965 - When I run "analizo metrics ." # -ok 966 - Then analizo must report that module Main has cbo = 1 +ok 966 - Then analizo must report that module Dog has noa = 1 # -# Scenario "Animals" project -ok 967 - Given I am in t/samples/animals/java +ok 967 - And analizo must report that module Cat has noa = 1 # -ok 968 - When I run "analizo metrics ." +ok 968 - And analizo must report that module main has noa = 0 # -ok 969 - Then analizo must report that module Mammal has cbo = 0 +# Scenario number of attributes in the "Animals" project +ok 969 - Given I am in t/samples/animals/java # -# Scenario "Animals" project -ok 970 - Given I am in t/samples/animals/csharp +ok 970 - When I run "analizo metrics ." # -ok 971 - When I run "analizo metrics ." +ok 971 - Then analizo must report that module Dog has noa = 1 # -ok 972 - Then analizo must report that module main has cbo = 1 +ok 972 - And analizo must report that module Cat has noa = 1 # -# Scenario "Animals" project -ok 973 - Given I am in t/samples/animals/csharp +ok 973 - And analizo must report that module Main has noa = 0 # -ok 974 - When I run "analizo metrics ." +# Scenario number of attributes in the "Animals" project +ok 974 - Given I am in t/samples/animals/csharp # -ok 975 - Then analizo must report that module Mammal has cbo = 0 +ok 975 - When I run "analizo metrics ." # -# Feature total modules -# As a software developer I want analizo to report the total number of modules in my code So that I can evaluate it -# Scenario Java Enumeration sample -ok 976 - Given I am in t/samples/enumeration +ok 976 - Then analizo must report that module Dog has noa = 1 # -ok 977 - When I run "analizo metrics ." +ok 977 - And analizo must report that module Cat has noa = 1 # -ok 978 - Then analizo must report that the project has total_modules = 3 +ok 978 - And analizo must report that module main has noa = 0 # -# Feature afferent connections with deep inheritance -# As a software developer I want analizo to report the afferent connections of each module So that I can evaluate it -# Scenario afferent connections of the dog family java sample -ok 979 - Given I am in t/samples/deep_inheritance/java +# Feature coupling between objects +# As a software developer I want analizo to report the value of CBO metric in my code So that I can evaluate it +# Scenario "Hello, world" project +ok 979 - Given I am in t/samples/hello_world/c # ok 980 - When I run "analizo metrics ." # -ok 981 - Then analizo must report that module Dog has acc = 7 +ok 981 - Then analizo must report that module main has cbo = 1 # -# Scenario afferent connections of the dog family java sample -ok 982 - Given I am in t/samples/deep_inheritance/java +# Scenario "Hello, world" project +ok 982 - Given I am in t/samples/hello_world/cpp # ok 983 - When I run "analizo metrics ." # -ok 984 - Then analizo must report that module DogFirstGreatGrandson has acc = 1 +ok 984 - Then analizo must report that module main has cbo = 1 # -# Scenario afferent connections of the dog family java sample -ok 985 - Given I am in t/samples/deep_inheritance/java +# Scenario "Hello, world" project +ok 985 - Given I am in t/samples/hello_world/java # ok 986 - When I run "analizo metrics ." # -ok 987 - Then analizo must report that module DogFirstPuppy has acc = 4 +ok 987 - Then analizo must report that module Main has cbo = 1 # -# Scenario afferent connections of the dog family java sample -ok 988 - Given I am in t/samples/deep_inheritance/java +# Scenario "Hello, world" project +ok 988 - Given I am in t/samples/hello_world/csharp # ok 989 - When I run "analizo metrics ." # -ok 990 - Then analizo must report that module DogGrandson has acc = 3 +ok 990 - Then analizo must report that module main has cbo = 1 # -# Scenario afferent connections of the dog family java sample -ok 991 - Given I am in t/samples/deep_inheritance/java +# Scenario "Animals" project +ok 991 - Given I am in t/samples/animals/cpp # ok 992 - When I run "analizo metrics ." # -ok 993 - Then analizo must report that module DogSecondGreatGrandson has acc = 0 +ok 993 - Then analizo must report that module main has cbo = 1 # -# Scenario afferent connections of the dog family java sample -ok 994 - Given I am in t/samples/deep_inheritance/java +# Scenario "Animals" project +ok 994 - Given I am in t/samples/animals/cpp # ok 995 - When I run "analizo metrics ." # -ok 996 - Then analizo must report that module DogSecondPuppy has acc = 0 +ok 996 - Then analizo must report that module mammal has cbo = 0 # -# Scenario afferent connections of the dog family java sample -ok 997 - Given I am in t/samples/deep_inheritance/java +# Scenario "Animals" project +ok 997 - Given I am in t/samples/animals/java # ok 998 - When I run "analizo metrics ." # -ok 999 - Then analizo must report that module DogSuperYoung has acc = 0 +ok 999 - Then analizo must report that module Main has cbo = 1 # -# Scenario afferent connections of the dog family java sample -ok 1000 - Given I am in t/samples/deep_inheritance/java +# Scenario "Animals" project +ok 1000 - Given I am in t/samples/animals/java # ok 1001 - When I run "analizo metrics ." # -ok 1002 - Then analizo must report that module Human has acc = 2 +ok 1002 - Then analizo must report that module Mammal has cbo = 0 # -# Scenario afferent connections of the dog family java sample -ok 1003 - Given I am in t/samples/deep_inheritance/java +# Scenario "Animals" project +ok 1003 - Given I am in t/samples/animals/csharp # ok 1004 - When I run "analizo metrics ." # -ok 1005 - Then analizo must report that module ShopController has acc = 0 +ok 1005 - Then analizo must report that module main has cbo = 1 # -# Scenario afferent connections of the dog family java sample -ok 1006 - Given I am in t/samples/deep_inheritance/java +# Scenario "Animals" project +ok 1006 - Given I am in t/samples/animals/csharp # ok 1007 - When I run "analizo metrics ." # -ok 1008 - Then analizo must report that module VenderShop has acc = 1 +ok 1008 - Then analizo must report that module Mammal has cbo = 0 # 1..1008 ok All tests successful. -Files=54, Tests=1627, 131 wallclock secs ( 0.42 usr 0.10 sys + 113.11 cusr 18.63 csys = 132.26 CPU) +Files=54, Tests=1627, 81 wallclock secs ( 0.48 usr 0.06 sys + 69.94 cusr 11.10 csys = 81.58 CPU) Result: PASS make[1]: Leaving directory '/build/analizo-1.25.4' create-stamp debian/debhelper-build-stamp @@ -5198,7 +5241,7 @@ debian/rules override_dh_auto_install make[1]: Entering directory '/build/analizo-1.25.4' dh_auto_install - make -j8 install DESTDIR=/build/analizo-1.25.4/debian/analizo AM_UPDATE_INFO_DIR=no PREFIX=/usr + make -j15 install DESTDIR=/build/analizo-1.25.4/debian/analizo AM_UPDATE_INFO_DIR=no PREFIX=/usr make[2]: Entering directory '/build/analizo-1.25.4' Skip blib/lib/auto/share/dist/Analizo/bash-completion/analizo (unchanged) Skip blib/lib/auto/share/dist/Analizo/README (unchanged) @@ -5206,95 +5249,95 @@ Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/profile.pl Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Test/Analizo.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Test/Analizo/Class.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Test/Analizo/Git.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Test/Analizo/Class.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Test/Analizo/BDD/Cucumber/Extension.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/auto/share/dist/Analizo/README Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/auto/share/dist/Analizo/bash-completion/analizo -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metrics.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Command.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/GlobalMetrics.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Extractor.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/ModuleMetrics.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metrics.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Model.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/ModuleMetric.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/LanguageFilter.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Model.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/GlobalMetrics.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/ModuleMetrics.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/LanguageFilter.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/FilenameFilter.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Extractor/Doxyparse.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Filter/Client.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Job.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Directories.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Output.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Runner.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Git.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Runner/Parallel.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Runner/Sequential.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Job/Directories.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Job/Git.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Output/CSV.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Output/DB.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/ResponseForClass.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/CouplingBetweenObjects.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/StructuralComplexity.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/NumberOfPublicAttributes.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/NumberOfChildren.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/LinesOfCode.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/LackOfCohesionOfMethods.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/MaximumMethodLinesOfCode.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/CouplingBetweenObjects.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/NumberOfChildren.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/NumberOfPublicMethods.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/NumberOfAttributes.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/NumberOfMethods.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/DepthOfInheritanceTree.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/AverageNumberOfParameters.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/NumberOfMethods.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/ResponseForClass.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/LackOfCohesionOfMethods.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/AverageCycloComplexity.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/NumberOfAttributes.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/NumberOfPublicAttributes.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/DepthOfInheritanceTree.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/LinesOfCode.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/AverageMethodLinesOfCode.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Metric/AfferentConnections.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/GlobalMetric/MethodsPerAbstractClass.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/GlobalMetric/TotalAbstractClasses.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/GlobalMetric/ChangeCost.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Filter/Client.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Extractor/Doxyparse.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Git.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Runner.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Job.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Directories.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Output.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Output/CSV.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Output/DB.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Runner/Sequential.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Runner/Parallel.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Job/Git.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Batch/Job/Directories.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Command/metrics_batch.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Command/graph.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Command/metrics_history.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Command/help.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Command/graph.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Command/metrics_batch.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Command/tree_evolution.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Command/files_graph.pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Command/metrics.pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metrics.3pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/Command/files_graph.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/GlobalMetric/TotalAbstractClasses.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/GlobalMetric/ChangeCost.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Analizo/GlobalMetric/MethodsPerAbstractClass.pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::AverageNumberOfParameters.3pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::LackOfCohesionOfMethods.3pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::AfferentConnections.3pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Command::files_graph.3pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::NumberOfAttributes.3pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::NumberOfChildren.3pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::LinesOfCode.3pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::ResponseForClass.3pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Command::help.3pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::NumberOfMethods.3pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo.3pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::CouplingBetweenObjects.3pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::DepthOfInheritanceTree.3pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::ResponseForClass.3pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::GlobalMetric::ChangeCost.3pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::AverageCycloComplexity.3pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Command::tree_evolution.3pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::NumberOfPublicMethods.3pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Command::files_graph.3pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::AfferentConnections.3pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::NumberOfAttributes.3pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::StructuralComplexity.3pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Command.3pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo.3pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::AverageMethodLinesOfCode.3pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Command::metrics_history.3pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Command::graph.3pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::NumberOfChildren.3pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::GlobalMetric::ChangeCost.3pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::CouplingBetweenObjects.3pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::NumberOfPublicMethods.3pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::NumberOfPublicAttributes.3pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Command::metrics.3pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Command.3pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::AverageNumberOfParameters.3pm -Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::LinesOfCode.3pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::AverageCycloComplexity.3pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metrics.3pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Command::metrics_history.3pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Metric::DepthOfInheritanceTree.3pm Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Command::metrics_batch.3pm +Installing /build/analizo-1.25.4/debian/analizo/usr/share/man/man3/Analizo::Command::metrics.3pm Installing /build/analizo-1.25.4/debian/analizo/usr/bin/analizo make[2]: Leaving directory '/build/analizo-1.25.4' rm -f -rv /build/analizo-1.25.4/debian/analizo/usr/share/perl5/Test removed '/build/analizo-1.25.4/debian/analizo/usr/share/perl5/Test/Analizo.pm' -removed '/build/analizo-1.25.4/debian/analizo/usr/share/perl5/Test/Analizo/Class.pm' removed '/build/analizo-1.25.4/debian/analizo/usr/share/perl5/Test/Analizo/BDD/Cucumber/Extension.pm' removed directory '/build/analizo-1.25.4/debian/analizo/usr/share/perl5/Test/Analizo/BDD/Cucumber' removed directory '/build/analizo-1.25.4/debian/analizo/usr/share/perl5/Test/Analizo/BDD' removed '/build/analizo-1.25.4/debian/analizo/usr/share/perl5/Test/Analizo/Git.pm' +removed '/build/analizo-1.25.4/debian/analizo/usr/share/perl5/Test/Analizo/Class.pm' removed directory '/build/analizo-1.25.4/debian/analizo/usr/share/perl5/Test/Analizo' removed directory '/build/analizo-1.25.4/debian/analizo/usr/share/perl5/Test' rm -f -v /build/analizo-1.25.4/debian/analizo/usr/share/perl5/profile.pl @@ -5323,12 +5366,14 @@ dpkg-buildpackage: info: binary-only upload (no source included) dpkg-genchanges: info: not including original source code in upload I: copying local configuration +I: user script /srv/workspace/pbuilder/76205/tmp/hooks/B01_cleanup starting +I: user script /srv/workspace/pbuilder/76205/tmp/hooks/B01_cleanup finished I: unmounting dev/ptmx filesystem I: unmounting dev/pts filesystem I: unmounting dev/shm filesystem I: unmounting proc filesystem I: unmounting sys filesystem I: cleaning the build env -I: removing directory /srv/workspace/pbuilder/29568 and its subdirectories -I: Current time: Thu Jun 8 02:16:48 -12 2023 -I: pbuilder-time-stamp: 1686233808 +I: removing directory /srv/workspace/pbuilder/76205 and its subdirectories +I: Current time: Thu Jul 11 10:41:43 +14 2024 +I: pbuilder-time-stamp: 1720644103