“…In summary, existing work present the following main limitations: (i) are dependent on models or other artifacts (e.g., FM or HCS architecture) that may not exist or be outdated [14,15,16,17,18,39,40,41]; (ii) require a failure-history or dynamic analysis [22,23,24,50,8], what is costly and may be not suitable for a CI scenario; (iii) do not consider HCS particularities and/or languages such as C and C++, largely adopted for the HCS development [26,27,28,49]; (iv) consider that there is a kind of mapping from code to the test cases or that the HCSs are developed following a specific format [22,25]; and (v) do not work with the concept of features, which are fundamental units of design and communication in the HCS context [46,47,48,29]. Our approach, presented in Section 4, addresses these limitations.…”