Here’s the list of the cool things that happened at TupiLabs since last Sunday.

• Updated Jenkins TestLink Wiki
• JENKINS-17689: Search box is missing
• JENKINS-17623: Jenkins Testlink integration broken in 1.9.6 version of testlink
• JENKINS-15937: TestLink Plugin prevents Jenkins from parsing Jobs
• JENKINS-13821: When test uses DataProvider it mark in TestLink only by last result
• JENKINS-17567: Allow the plug-in to filter test cases by last execution status
• JENKINS-16640: Mark in Jenkins build with “NOT RUN” Test Cases and display in the UI (with colours, etc)
• JENKINS-17622: Cannot access TestLink environment variables within Jenkins build
• Released Jenkins TestLink Plug-in 3.4
• Released Jenkins TestLink Plug-in 3.5
• Added more expressions to Speak Like A Brazilian
• Added a blog to Speak Like A Brazilian using PieCrust and CodeIgniter (we’re writing a blog post about it!)

We are working for you

Have a great week! :-)

Here’s the list of the cool things that happened at TupiLabs since last Sunday.

• Released testlink-java-api 1.9.6-1
• Released Jenkins TestLink Plug-in 3.3
• Sent a request of merge for TestLink gitorious
• testlink-java-api #6
• testlink-java-api #5
• Updated testlink-java-api SourceForge.net website
• Added more expressions to Speak Like A Brazilian
• Meeting with prospect for a Jenkins project
• Fixed bug in TupiLabs website with paginations (big thanks to José for that!, see this post for details)

Have a great week!

Here’s the list of the cool things we did since last Sunday at TupiLabs.

• Some issues and pull requests for Jenkins TestLink Plug-in
• A new pull request and a weird bug reported via e-mail in Jenkins TAP Plug-in
• New Likes at our Facebook page for Speak Like A Brazilian. Yay!!!
• Vectorized some potential Frege logos and sent to the project mailing list
• We have finished a small NLP and Big Data prototype for a prospect. The presentation will happen in the next days at the customer site!
• Research work for Paskuale backend
• Garagem Vaga received a new parking lot, and we are working on the marketing and promotion material

We are working for you

Have a great week! :D

This is an interesting case that I received via e-mail from G. M. after he read the post . Basically, using an approach similar to the testlink-plugin for Jenkins, one could send the coverage results to TestLink.

TestLink has requirements x test case coverage information, and Sonar, Jenkins, Cobertura and other tools give you source code x test coverage. Crossing these information could be interesting.