Content Creation Guidelines

Our purpose with Content Creation is to support the technical development of the TesterWork community members, current and future, with the knowledge and insights we share in our blog.

Diving into our Blog Articles

Before starting your next article, we strongly recommend that you read the ones that have been already published by other testers to understand the type of content we seek, how to develop the theme, and the text structure. By reading posted texts, you also avoid writing about a repeated topic. Just keep in mind that the type of content and structure of articles we are aiming for have been updated.

Reproducibility Testing: A Complete Guide

The History of Software Testing

Smoke Testing: A Complete Guide

How to Write Legendary Bug Reports

Test Coverage Strategies for Comprehensive Testing

Understanding the audience

Blog readers are registered testers on Tester Work or individuals who find the texts through Google searches. Our main focus is on QA testers and manual testers, but we also reach people in the IT field, Quality Assurance in general, and software development.

Guidelines

Aiming to help you with your article production, considering SEO strategies and a deep understanding of the field and audience, submission rules were created. Here we share them to improve blog posts results and give you visibility on the criteria we use to approve the articles. 

As part of our ongoing effort to enhance the quality and uniqueness of the content on our blog, we're excited to introduce a new approach for article submissions - Case Studies. We expect that you write about test cycles in which you worked on at Tester Work (or other QA projects you worked on elsewhere).

Structure

• Title
  • Make it catchy and descriptive, summarizing the key aspects of the case study.
• Introduction
  • Briefly introduce the project or test cycle being discussed;
  • Do not disclose sensitive information that could compromise security or violate privacy agreements (like clients/products names);
  • Describe:
    • Testing effort (number of hours it took you to complete the execution);
    • Type of device required;
    • Project Type (Test Case Execution, Exploratory, Usability, TC + ET);
    • Product type under test (web3 gaming, cryptocurrency transaction, cash in flow, etc.) - you can either categorize or describe it;
  • Mention the goals and objectives of the test (translation, find as many bugs as you can, test the payment flow, etc.).
• Challenges
  • Identify and discuss the specific challenges faced during the testing process (reproduce the bugs, find bugs, classify their severity, test case complexity, localization or cultural adaptation barriers, etc.);
  • You can share what are the most common types of bugs encountered in the cycle and their severity;
  • You can describe what were the expected results versus what were the actual results found;
  • Include unexpected issues, if encountered.
• Approach/Strategy
  • Describe the testing strategies and methodologies you employed to address the challenges.
• Results
  • Provide insights that can be valuable for other testers and QA professionals;
  • Explore how this test potentially impacted the customer's business, sharing possible results and improvements for the products.
• Conclusion
  • Summarize the key takeaways from the case study.

Optional: Provide links to relevant resources or forums for further discussion.

Text length

• The text must have a minimum of 300 words;
• Most importantly, ensure the content is rich and comprehensive.

Title selection

• The title must be direct and clearly relate to the content developed in the text;
• To choose the title, think about how the audience would search for this content on search engines;
• The title must have between 40 and 70 characters. A character is any text unit (letters, numbers, punctuation, or spaces);
• Choose the title based on the most important term in your text, which will be used once or several times throughout the text.

Writing the text

• The ideal text consists of: title, introduction, subtitles, body of the text, conclusion, and references;
• Develop your article in bullet points, using subtitles to organize your text into parts and make the reading more dynamic;
• Plagiarism is prohibited, and if it occurs, it is the responsibility of the text author;
• To avoid issues of indirect plagiarism (when having the same idea as another text but with different wording), include at the end of the text the references you used to acquire that knowledge and develop the article. Use relevant, recognized, and authoritative references;
• Ensure the text is not repetitive in its content. Use subtitle and paragraphs to create a development and evolution of the content line, instead of talking about the same topic repeatedly;
• Avoid very long paragraphs. Use punctuation and connectors to write shorter paragraphs (a maximum of 4 lines per paragraph).

Sending the article

• When submitting your article on our Support Centre, please attach the file downloaded in .docx format.

Sharing the knowledge and experience you have built is a key step to the advancement of the QA testing field. It involves you as part of a community committed to excellence in software quality and collective growth.

Follow these guidelines to showcase your expertise and elevate your professional standing.