Program to calculate a student's test average
Here are some comments regarding how I would approach this:

Coding Style 


Avoid using comments to document things that are evident: For example, "Getter for average" is not needed when the method is a very standard getAverage method, which most people will know what is and what to expect from it. You will find many different positions on this topic, but I try to add comments just for situations where the purpose of the code is not evident, or something is used/done in a not very standard way. 
Code separators: I wouldn't recommend using separators like the one you ask about for separating portions of code. IT is not very standard, and the code separation should come from good class and method definitions, and not from artificial elements. 


Main Programing Considerations


Requirements and Objective: always start with clear objectives and requirements. In your case, I would say (from your comments) that it is to calculate the average score for your students. This is important because it allows you to focus on what's required, and avoid what's not needed. 
Constructor: as you ask in your comments, probably the best way to create a Student is not doing it with a "blank" object, which is what you do when you don't use a constructor to set its initial state. Passing the student name to the constructor would be a better way to initialize this type of object, because there's no point (in this particular case) to create an instance of Student that has no name and belongs to nobody. 
Extensibility: the way things are now, adding a new test would require more code than I would like. Adding 10 tests would require a lot of code. I would approach this using a collection of Tests, and would decide which methods I really need to supply the required functionality. 
Decomposition: as your comments suggest, each Test can have it's own score and weight. I would create a Test class to keep those attributes (I would also consider adding a Name property to identify each test easily (in case I decide to print or produce the full Test summary for the Student).
Getters and setters: it is ok to have getter and setters for your class properties, but just because you have properties doesn't mean you need to provide setters and/or getters for them. I would choose for which properties I really need to have getters and setters, according to your objectives and requirements. Some properties can be modified and consumed internally (only from within the class), and that's fine. By choosing wisely the public methods each class provides (the class API), you simplify the class API, which IMHO is always desirable. 


With this comments in mind, this is the code I produced to solve your problem:

Application.java

public class TestCases {  
    public static void main(String[] args) {
        Student student1 = new Student("Bob");
        student1.addTestScore(new Test("test1", 80, 0.25));
        student1.addTestScore(new Test("test2", 60, 0.25));
        student1.addTestScore(new Test("final", 90, 0.5));

        student1.printStudentTestSummary();
        student1.printStudentTestAverage();
    }
}  


Student.java

public class Student{

    private String name;
    private ArrayList&lt;Test&gt; tests = new ArrayList&lt;&gt;();

    public Student(String name) {
        this.name = name;
    }

    public void addTestScore(Test test) {
        tests.add(test);
    }   

    public void printStudentTestAverage() {
        float average = 0;
        for (Test test: tests) {
            average += test.getWeightedScore();
        }
        System.out.println("Test average for student: " + average);
    }

    public void printStudentTestSummary() {
        System.out.println("Test scores for student: " + name);
        for (Test test: tests) {
            System.out.println(test.toString());
        }
    }
}


Test.java

public class Test {

    private String name;
    private int score;
    private double weight;

    public Test(String name, int score, double weight) {
        this.name = name;
        this.score = score &lt; 0 ? 0 : score; // basic check for valid score
        this.weight = weight &lt; 0 ? 0 : weight; // basic check for valid weight
    }

    public double getWeightedScore() {
        return score * weight;
    }

    public String toString() {
        return "Test: " + name + ". Score: " + score + " (w " + weight * 100 + "%).";
    }
}


Finally, see that you can now add more complex validations to scores and weights, if needed. You can easily extend this code now to support additional use cases also. 

Hope this helps!