Page History
...
Within each area/topic, tips will be presented by descending order of risk; each tip is preceeded by a icon that corresponds to the risk level.
Legend:
- major
- highest
- high
- medium
- low
- lowest
Process
- "Unified" development process: define a process that can be applied to all teams in the way how to manage the STLC. Every team is different and has its own needs, therefore your process should not be too strict but it should provide some guidance on how development life cycle should be addressed, covering requirement management, bug management and test management. Having teams working completely in different ways, hardens communication and leads to unproper and unoptimized tool usage. If you have a well-defined process that can be used organization wide, better; this is the key to ensure an optimal usage and have the best performance.
- Are you adopting Agile and Scrum? Check out Using Xray in an Agile context for tips on how you can take advantage of Xray in such scenarios;. Agile software development page provides high-level overview of Agile and Agile Testing and besides background information on them, it will also provide some useful tips so your team can be more Agile and avoid doing things that are unnecessary.
Specification
??
Organizing
- If you have thousands of Tests, using the Test Repository approach may provide additional benefits over using "lists" (i.e. Test Set issues), as it makes management of test cases easier while avoiding the creation of issues.
Planning
...
- Instead of creating one Test Plan for your release, you may create multiple Test Plans to track different Tests
...
- (e.g. manual vs automated); this may be useful if you want to have clear visibility of how certain groups of Tests are progressing and if their execution lifecycle is different from other ones
...
- . It will also make your Test Plans considerable lighter.
- If adopting Scrum, create Test Plans per Sprint, to track the testing being done in the scope of your Sprint
...
- ; manage them as artifacts of your Sprint and add them to your Scrum boards so everyone sees their progress. Per each Sprint you may have more than one Test Plan; check out some possible usage patterns here.
Execution
??
Entities
Requirements
...