Getting Involved

Session Tester needs help from programmers, testers, business analysts and technical writers. You are free to join the community and contribute in whatever role suits you. You are welcome if you share the vision of the tool, and:

• want to learn and contribute to a tool where your work can be shown publicly
• be part of an open, free community that will provide you with feedback on your work
• would like to help develop a tool for testers to help them improve their work
• are willing to be accountable to your community of peers

Benefits to Contributing:

• this is a real tool, used by people who will give you feedback on what they like
• contribute to a tool that has a user community from all over the world
• you don't have the time pressures of a day-job, so you can explore new technology and work at your own pace
• have a public example of your work that you can use when you are trying to get work
• have the opportunity to learn new technology
• try out a different role than what you are committed to in your career
• you will work with world-class people on a fun project
• as part of a self-critical community, your peers can give you work references if you excel as a team member

Time Commitments

There are no minimum requirements for contributing to Session Tester. If you are interested in an area, contact the team and sign up to work on what you are interested in doing. If Commit as little or as much time as you feel you can. Some people may have an hour or two a week available, while others may have more time. Still others may only have an hour or two a month to contribute (or less). All of that is just fine.The only thing we ask is that if you cannot make a commitment, let the team know so we can have someone else complete it.

Community Involvement

The purpose of this project is to provide a much-needed tool to the Session-Based Testing space. However, we believe this should be a fun learning experience for you. Look at the project as a place to learn and contribute without the pressures of work.

Overall, we want this to be fun and an opportunity to learn. Currently we are using the following technologies:

• Java
• SwingUIBuilder (for the GUI)
• XML (for persistance)
• HTML/CSS (for reports)
• XQuery (what we will use for reporting from XML sources)
  If you'd like to learn how to use these technologies better, or to test using something that is different from what you are used to, feel free to join up and commit to as much or little time as you are comfortable with.

I have a better idea!

Ideas and Prototyping

If you have an idea on the direction the tool should go that is outside of the directives from JIRA or the roadmap, feel free to prototype it and share it with the development team. If we like it, it will get incorporated into the tool. Prototyping and sharing design ideas with the community is a big part of the development culture on this project. Our project founder (Jonathan) comes from a long history of iterative/incremental projects from RAD, Spiral, then on to Agile such as XP, Scrum, and others. It's a good idea to prove or disprove the value of ideas by trying them out rather than debating.