m-zakeri / d4t

Design for testability

D4T: Design for testability

This repository contains the source code and replication package for our creative learning-based ‘design for testability’ approach in software systems. More information is available at https://m-zakeri.github.io/D4T.

Note: The full implementation will be available after our relevant paper(s) are published.

d4t's Issues

convert class diagram graph to CDG(class dependency graph)

Test class_diagram and fix bugs.

check class diagram with output of understand.
It seem class_diagram module does not handle abstract dependencies.

Using template for Dependecy injection

Complete the dependency injection pattern with a template described in the following references:

[1] How to create your own Dependency injection framework in Java
[2] Inversion of Control Containers and the Dependency Injection pattern

Factory detection bug.

In the following example factory can not detected.
if we remove "implements Y" this can detect factory but if we keep it this algorithm can not detect factory pattern in this example.

example:

package com.products;
import com.functions.DecodedImage;

class X
{

}

interface Y
{

}

class GifReader extends X implements Y{
private DecodedImage decodedImage;

public GifReader(String image, int size) {
    this.decodedImage = new DecodedImage(image);
}

public DecodedImage getDecodeImage() {
    return decodedImage;
}

public int getEncodeImage() {
    return 0;
}

}

add "create" label to class diagram graph

we need detect create uses.

Statistical analysis

Write some scripts that show the following data:
1- number of detected factory pattern
2- number of injection pattern detected in each case(case1, case2, case3, total)
3- compute complexity for each project or package(in very big project).
4- Find best sensitivity(hyper parameter in factory pattern).
5- Show some useful charts and analyze them.

Import dependencies

dependencies does not import in Injector.java files.

Class Diagram Bug(set_stereotypes)

after refactor factory pattern in "10_water-simulator", when we want to make class_diagram of refactored code return bellow error:

File "/media/sadegh/Data/sadegh/iust/compiler/compiler projects/main_project/class_diagram.py", line 652, in __calculate_interface_modification_type
if method_info[class_name]['methods'][m]['is_modify_itself']:
KeyError: 'getInstance'

Factory method extended or abstract class does not handle.

We have 2 case in this issue:
1- Imagine that we have products that extends a class that have products-common-methods so in this case we must make a interface from extended class and use this interface in creator class.

2- Imagine that we have products that extends an abstract class, if abstract class does not have non-abstract method we can replace it with an interface and use that interface in the creator class.

add complexity matrix

Add complexity matrix to compute test effort.